 | | Re: Two questions on primitives
|
|
Thanks guys. You cleared up my only question with BFC -Orion (23 years ago, 30-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| |
| | Re: Online Mac instructions.
|
|
What is the problem with case exactly on macLDGLite? The linux parts distribution has different case directory names and ldglite has a problem with that? Is it just the directory names that are trouble? LDRAW has the same notion of case as DOS, (...) (23 years ago, 30-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Online Mac instructions.
|
|
As case sensitivity, I haven't changed the actual parser code, so if the directory names are in upper case then it should work. However I must confess I haven't tried using the linux ldraw primitives, so to redress this, I have just downloaded the (...) (23 years ago, 30-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Online Mac instructions.
|
|
(...) From my experience, I think thats correct. Whatever case you create something as is the actual case that it is stored as. But, the ability to open a file is 'case insensitive'. Therefore, while it does preserve case when creating a file, you (...) (23 years ago, 30-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Online Mac instructions.
|
|
(...) I have to admit, I'm stumped on this one. According to several sources on the internet, the Mac HFS filesystem is case preserving for writing, but case insensitive for lookups. And since the OS 8-9 ldglite code seems to be using stricmp for (...) (23 years ago, 30-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Two questions on primitives
|
|
(...) You've got it. When existing part files are made BFC-compliant, they have to be checked through completely. The main changes are fixing polygon wrapping and adding INVERTNEXT statements. Until a file is labeled BFC-compliant, renderers (...) (23 years ago, 30-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| |
| | Re: Two questions on primitives
|
|
(...) Is this a real issue? Parts can't be truly BFC compliant until all of their subparts are BFC compliant. So yes, you'll have to insert those INVERTNEXT commands. But the part wasn't BFC compliant before, and this is just another part of (...) (23 years ago, 29-Mar-02, to lugnet.cad.dat.parts, lugnet.cad.dat.parts.primitives, lugnet.cad.dev)
|
| |
| | Re: Optimising piece use (Was: LDraw.org MOTM/SOTM voting for March is open)
|
|
Cool. I like the parallel-paths-to-ground idea that you'd get with conductance and studs as resistors. I can see large 1x16 "ground plane beams being used, likewise maybe wall pieces. Another interesting aspect is surface gradients, and the use of (...) (23 years ago, 29-Mar-02, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Online Mac instructions.
|
|
(...) Yeah, but it is the ONLY editor we Mac users have. So it is the best and most popular Mac ldraw app. I know what you mean, you don't want us to think that it is the ultimate. It is just that we can't even put up a "getting started" page if (...) (23 years ago, 28-Mar-02, to lugnet.cad.dev.mac)
|
| |
| | Re: LDAO Editor Error & Crash
|
|
(...) Hmm. I'm guessing it's coming across something it doesn't like in the ldraw.ini file. You could try temporarily renaming this file, then trying to access Options | View Settings. Just to see if that lets you in. I seem to remember that this (...) (23 years ago, 28-Mar-02, to lugnet.cad.dev)
|
