 | | Re: 11-16 primitives?
|
|
(...) If it's running in Windows, I think a backwards-compatible switch should use the Win32 API to get the short filename (with the ~1 at the end, usually, determined using PathGetShortPath) and use that in place of the long filename. --Travis (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) That would be good, I think. (...) Can you have two levels? Level One that still shows the warnings, but doesn't stop, and Level Two suppresses all warnings. (...) I'd keep the current line-format for all parts conforming to the 8.3 format, (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I could update the mklist sources to work handle filenames with 25 chars I was going to add a quietmode commandline option this weekend anyhow. Should I allow 25 chars as the default, and perhaps include an optional command line arg to (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) If I understand that, this would mean that we could use a new mklist tool and we can start using that long filenames. The possibility to use MLCad for generating PARTS.LST will be away, but this only a little cut. cu mikeheide (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Were any other issues anticipated? (...) I did a short test of MLCAD with a modified PARTS.LST. The results were mixed - MLCAD seems OK using an altered-format PARTS.LST file, but re-generating PARTS.LST from MLCAD results in an invalid file. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) When the LSC updated the spec to allow 21.3 filenames, I don't think any of us were aware that this would create a problem for PARTS.LST. However, looking at the file, there's a chance that MLCAD will work perfectly well with longer filenames (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Parts Tracker-wise (if I remember right, and if nothing's been changed), there's only one script which needs to be modified to accept 21.3 files instead of 8.3 files. Organizationally, I dunno if there is actually a hold-up. The specifications (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) This is the status quo now for many months. What action has been taken to solve that problem? To me it seems only to be a little adjustment to some lines of code (but maybe I am wrong). So my question would be: where is the bottleneck that (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Well... imho this should not be an issue at all - if the parts tracker was updated! Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) These truncated filenames never went past the LSC, and as such should probably be held. I personally feel that they are inappropriate, but whether or not I think they are appropriate, I believe that it's the LSC's job to determine that. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
Hi Steve, (...) One reason: the Parts Tracker still doesn't like >8 names :( Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I ditto Phillippe's primary suggestion: use multiple files. It's good for multiple reasons. However, the current standards allow at least 25 characters in the filename, so is there a reason to worry about a 9 character primitive name? Steve (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I would suggest avoiding the problem completely by using a 2-4edge + 3-16edge... In other instances the name was shortened: 3-16cone19 --> 3-16co19 11-48ring19 --> 11-48r19 Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | 11-16 primitives?
|
|
What would be the suggested name for an 11-16 primitive for a cylinder or edge line since 11-16 contains 5 letters and tacking on edge or cyli at the end would give a 9 letter name? (15 years ago, 22-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Reverse Ratio torus naming convention
|
|
I have endorsed the Primitive Generator's naming convention for "reverse ratio" tori (toruses) with a minor update to the Primtives Reference ((URL) of the form r{ff}o{rrrr}.dat represent the outer section of a torus where the minor radius is (...) (15 years ago, 21-Jun-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Reverse torus naming convention
|
|
I have endorsed the Primitive Generator's naming convention for "reverse ratio" tori (toruses) with a minor update to the Primtives Reference ((URL) of the form r{ff}o{rrrr}.dat represent the outer section of a torus where the minor radius is (...) (15 years ago, 21-Jun-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders [DAT]
|
|
(...) There is no way to get your shape using primitives, it would require non-linear transformations. So, as mentionned by Michael, the best way is to use Coverer. You can nonetheless get a similar (but quite different) shape using shearing as (...) (15 years ago, 15-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders
|
|
Is this what you had in mind? (...) Basicly changing any of the non zero coordinates will scale along the coresponding axis. You can also accomplish shearing by replacing any of the zero's with a different number. (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders
|
|
(...) AFAIK there is no solution with primitives in this case. I would suggest use one of the tools from Philo ((URL) to fill the space between those 4-4edge.dat cu mikeheide (15 years ago, 15-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Stretching cylinders [DAT]
|
|
Well, it's my second thread today, but how would you go to "stretch" a cylinder, like a cone, but only in Y-axis, not X-axis? I've again attached a dat file to show what I mean. Basically I'd need a cylinder that'd fit those two 4-4edge.dat:s, any (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
