 | | Re: Line in the Sand [DAT]
|
|
Jacob Sparre Andersen wrote... (...) (snip) (...) Why? Are you thinking about 1 16 -4 0 0 0 0 0 0 0 4 1-4disc.dat The determinant is zero, which BTW causes POVRay to halt ("singular matrix"). L3P has to fix these matrices or POVRay would not render (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: LGEO homepage ?
|
|
Todd Lehman wrote on December 17th: (...) I have tried to get in contact with Lutz for the last two months regarding LGEO+L3P. None of the mails were bounced, latest attempt was 15. december - the day before Todd's mail was bounced. /Lars (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Line in the Sand
|
|
Steve Bliss wrote... (...) I think this is a possible, but rare case. It can, however, be circumvented by regarding DAT files from PARTS as special. (...) Why not? Any information you can gather by simply analysing a DAT file should not be required (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: General Comments to MLCad
|
|
(...) Ahh, "tagged" information then, in other words? :) Cool....... --Todd (25 years ago, 20-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: The updated PARTS.LST online?
|
|
(...) Try (URL). It's not searchable (yet), but it is browseable. Steve (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: General Comments to MLCad
|
|
(...) It would be better (IMO) to format non-LDraw information as LDraw-style meta-commands, and keep everything in the DAT format. That gives the file the widest transportability between programs. Steve (25 years ago, 20-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: The updated PARTS.LST online?
|
|
(...) It is? Well, duh. Thanks for the info. Anyway, I still think that a browsable parts.lst could be a good idea. Sometimes I have the need to look up a part name or number when I'm not on a system with LDraw on it, and I think perhaps others may (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: The updated PARTS.LST online?
|
|
(...) An updated parts.lst is included in every parts update. Steve (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: The updated PARTS.LST online?
|
|
(...) Sounds like a good idea. Would /download/updates/ be appropriate for this? And does anyone have a non-butchered current parts.lst (unlike mine) they'd send for this? I'll get it up at least by Thursday, when I update the MOTM voting. -Tim (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | The updated PARTS.LST online?
|
|
I think it would be a good idea to make the updated PARTS.LST file be available online as new releases are made. I know that the PARTS.LST file should be remade on the local system as the new parts are installed, but I still think it would be nice (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
This seems to be a bug, I will look at it, beside this I will take over the strategy suggested by Bram with using COLOR meta commands ... Michael Will Hess wrote in message ... (...) in (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
Michael, I can understand the need to use hex to define custom (non-TLC produced) colors, and I'm sure that you'll find a way to fix this. What I'd like to know is why the transparent versions of the standard colors are now saved in this manner. Now (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Loader)
|
|
(...) I suggest defining the custom colors the way LDLite does, ie: 0 COLOR ... That way, you can still use the color numbers in the .dat lines so that the file will still work in LDraw and LEdit, except that the colors will be off. --Bram Bram (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: General Comments to MLCad
|
|
(...) Could you avoid writing out the file as a ".DAT" file extension if you are making extensions to the long established LDraw DAT file format? This would clear up confusion right away and avoid further incompatibility issues if other LDraw-clone (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
I thought LDLite is able to display this colors! If this is realy a problem I can change this to use comment lines defining these custom colors! Todd Lehman wrote in message ... (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | hex values (was: Re: Loader)
|
|
(...) Wonderful. So why does MLCad insert nonstandard data into LDraw DAT files? --Todd (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Another part variation
|
|
In lugnet.cad.dev, Steve Bliss writes: [snip] (...) Yeah, it's kinda wild. Do you think TLC have a list with individual names and numbers for these 3 different parts? They must. How else could they get the right thing in the little baggies. It sure (...) (25 years ago, 18-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Another part variation
|
|
(...) Given that the 2 parts are different mabie we need a technic horn in the ldraw library??? -- Jonathan Wilson wilsonj@xoommail.com (URL) (25 years ago, 18-Dec-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Old Parts replaced by Newer Versions?
|
|
(...) I (...) has (...) Actually Chris, I think I have either all three versions or at least the last two in gray. The delicate ones came with 2 Space Dart-Is I bought over a 15-year span. Ironically, it was a thicker, more durable clip that I had (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Another part variation
|
|
(...) Augh! You're right! I've got three different versions, right here on my desk. Specifically, I've got: Brown tree trunks, height = 44LDU, no internal teeth/tabs Brown tree trunks, height = 40LDU, no internal teeth/tabs Black tree trunks, height (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev, lugnet.general)
|
