 | | 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)
|
| |
| | Technic part file title issues and suggestions
|
|
It's this time of year again where I've got a bunch of part naming issues: - There are two official and a set of unofficial Technic Excavator Bucket parts. The problem just is that the buckets' don't only work as excavator buckets; front loaders, (...) (15 years ago, 17-Sep-09, to lugnet.cad.dat.parts)
|
| |
| | Re: 64179.dat
|
|
(...) Ah!!! interesting ;o) (...) It looks good (but I don't have the part - yet...) Philo (15 years ago, 11-Sep-09, to lugnet.cad.dat.parts)
|
| |
| | 64179.dat
|
|
Yes, I did state at (URL) that I couldn't model this piece due to my lack of it - but the Front Loader appeared convienently (sp?) in the store and I had all the cash for it, so... now I have modelled the 'O-beam' as well. Enough story-telling: I (...) (15 years ago, 9-Sep-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | POV dat for L3P v1.4 - 3626bpse - Minifig Head with SW Scout Trooper Black Visor Pattern - POV [DAT]
|
|
Ok, so now I've found out why my minifig head dats with inline POV no longer work. New POV-Ray version was no problems this time. But two changes frm L3P 1.3 to 1.4 caused problems: The names of the colors have been changed from Color[n*] to (...) (15 years ago, 11-Aug-09, to lugnet.cad.ray, lugnet.cad.dat.parts)
|
| |
| | Looking for 64651.dat and 64645.dat files
|
|
I am looking for: 64651 Boat Base 13 x 16 Stern/Bow (URL) 64645 Boat Base 10 x 16 Stern/Bow (URL) LDraw files thanks kurt (URL) The Home of Republic of Texas Navy in LEGO> (15 years ago, 6-Jul-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Looking for 64651.dat and 64645.dat files
|
|
Hi I am looking for the new 64651 Boat Base 13 x 16 Stern/Bow 64645 Boat Base 10 x 16 Stern/Bow (4 URLs) DAT files thanks kurt (URL) The Home of Republic of Texas Navy in LEGO> (15 years ago, 6-Jul-09, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Help working the Non-CA and L(EGO)Draw parts queue
|
|
(...) Thx for pointing to - must have slipped my eagle eyes ;-) w. PS. And thx for polishing the Mechanical Arm Straight. (15 years ago, 24-Jun-09, to lugnet.cad.dat.parts)
|
