|
|
 | | Re: colors completeness
|
| (...) I've been making an effort recently to demonstrate that LDView (including the development version, 3.2) will work on the Mac. Although LDView 3.2 itself is, as you emphasize, unreleased, the source code is available, so I've been trying to (...) (18 years ago, 3-Mar-07, to lugnet.cad)
| | | | | Re: LDView 3.1 on Mac OS X!
|
| (...) Absolutely. But until such time as a program like that is available, I'm most interested in what can be done pragmatically with the tools available now. I've probably just confused the discussion of plans for future improvements - in which (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac, FTX)
| | | | | Re: LDView 3.1 on Mac OS X!
|
| (...) Well I would argue that is forcing the user to do something the program could do much more easily (and accurately). Both those make the assumption that the contents of the standard LDraw directory are always official, and the contents of the (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac, FTX)
| | | | | Re: colors completeness
|
| (...) Then I would definitely recommend LDView for the rendering chain. I've recently used it to create a set of part images (as I used to use ldglite) for the entire library, and they are FAN-TAB-u-Glorious! Travis has been very helpful, and even (...) (18 years ago, 3-Mar-07, to lugnet.cad)
| | | | | Re: colors completeness
|
| (...) Well the problem with bleys is that L3P doesn't just replace them, it deletes them. Fortunately it doesn't seem to have this problem with parts in colours greater than or equal to 256. Fortunately, l3p colour definitions check to make sure the (...) (18 years ago, 3-Mar-07, to lugnet.cad)
|
|
