To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / *4010 (-20)
  Re: parts.lst and mklst(?).exe.
 
(...) The default behavior is to be case insensitive but you can set an option to make it case sensitive, take a look at the man page for mount. Leonardo (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: Line in the Sand
 
(...) I do, it's because of those cases like an hollow cylindir DAT file is referenced by another DAT file. Since the cylinder is supposed to be define outwards, but you can use it to make the inside/outside of a stud (for example) and the if the (...) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: Line in the Sand
 
Steve Bliss wrote... (...) :-) Jean-Pierre's analyzer is not a "simple analysis" and may not work 100% correctly without human intervention. /Lars (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: Line in the Sand
 
Steve Bliss wrote ... (...) Is this a joke? You argue very well in "Inversion" in "Language Extension Functionality" about the 3D tube ;-) /Lars Sorry if I missed a pun. (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: parts.lst and mklst(?).exe.
 
Johannes Keukelaar wrote... (...) It does work, you can open either 1234a.dat or 1234A.DAT, or even 1234a.DaT. The fat/vfat/msdos filesystem in Linux is case-insensitive. Try it! (...) Pure MSDOS programs see all files in uppercase. /Lars (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: parts.lst and mklst(?).exe.
 
(...) I believe that straight-DOS programs don't have mixed-case filename information. A pure DOS hard-drive actually stores all filenames on the harddrive in upper case, and MSDOS under Windows maintains upper-case-only for compatibility with older (...) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: General Comments to MLCad
 
(...) Yep. LDLite does things like 0 COLOR <color definition information> along with other stuff, and the HTML instruction generator in LDAO recognizes a subassembly statement: 0 SUB <file> <layout options> and in lugnet.cad.dev, we're proposing to (...) (25 years ago, 21-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
 
  Re: Line in the Sand
 
(...) In that case, why are we wiggling about with this BFC extension stuff? Rendering programs can figure out what order vertices should be put in, and they can figure out which way a polygon is facing. They don't need all this extra effort from us (...) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: Line in the Sand
 
(...) Matrix-inversions are not evil. But for some reason, using them to actually invert subfiles is evil (as opposed to using INVERTNEXT to invert subfiles). If I reallly needed an answer to this, I'd go read past messages. But I *do* remember: a) (...) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: ldraw.org parts refernce list..
 
(...) LOL, gosh Tommie [1], just cause I said 'it doesn't phase me' on AIM regarding different (diminutive) spellings of my name, doesn't mean you have to go public and address me as that ;) [1] <ducks, runs> :) -Tim (URL) timcourtne ICQ: 23951114 (...) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  parts.lst and mklst(?).exe.
 
Hi all! The other day I was working a bit on a program that can parse dat files under linux. Now, I have my dat files, along with ldraw and mlcad installed on a Windows partition. All the dat files that come with the ldraw package and updates there (...) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  ldraw.org parts refernce list..
 
i am making a parts reference list for timmy / timothy / tim ( :)--- ) c. there are parts i know, that are not on lutz list, and are not in ldraw. if anyone has some part #s please mail them to me? (those are MOSTLY in 30000 range) (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  Re: LGEO homepage ?
 
(...) I've just tried to access the page and it's working again. Leonardo (25 years ago, 21-Dec-99, to lugnet.cad.dev)
 
  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)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR