 | | Re: In dev: new ldconfig.ldr file —Steve Bliss
|
| | | (...) I'd say we're getting to the point where -- if there are going to be more than a handful of color configurations -- we'd want to think about some alternate distribution/management methods for 'color configurations'. Similar to what other (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| | | |
| | | | | Re: In dev: new ldconfig.ldr file —Kyle McDonald
|
| | | | | (...) That sounds sensible. Also it's occurred to me since my last post on the internationization topic, that the Color names, and color definitions might be better off split up. 1. If the skins or theme's catch on, there's no sense having a (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: In dev: new ldconfig.ldr file —Steve Bliss
|
| | | | | | (...) Yes ... and no. If we did produce a fully internationalized, multi-namable color definition set, we'd almost certainly include a 'default name' property for the colors. So think of the data in ldconfig.ldr as the color definitions + the (...) (20 years ago, 11-Aug-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: In dev: new ldconfig.ldr file —Tore Eriksson
|
| | | | (...) The more I think about it, the more I lean towards ldconfig.ldr should stick to handle just 'color definitions' and just default border colors, rather than 'color configurations'. Where 'default' is the traditional "anti-color" that optionally (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: In dev: new ldconfig.ldr file —Travis Cobbs
|
| | | | | (...) <SHAMELESS_PLUG> That's easy, just use LDView ;-). </SHAMELESS_PLUG> It won't let you turn off all type 2 lines, but it will let you turn off all "edge lines", which are all type 5 lines, and all type 2 lines that are color 24. To be honest, I (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: In dev: new ldconfig.ldr file —Tore Eriksson
|
| | | | | | (...) The very big problem with all the nice options in L3Lab is that they aren't saved anywhere. One place to put all those options stored would be the ldconfig.ldr file, but I think it would be more natural to put it in ldraw.ini or a (...) (20 years ago, 10-Aug-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: In dev: new ldconfig.ldr file —Travis Cobbs
|
| | | | | | (...) Well, if you look at Datsville a lot, that would probably be the reason. It won't open in any version of LDView released to date. The next major LDView release (3.0) will open it. I just opened town.dat, and while it took 25 seconds to load (...) (20 years ago, 10-Aug-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | Re: In dev: new ldconfig.ldr file —Steve Bliss
|
| | | | (...) I agree that ldconfig.ldr should stay simple. But it should be possible for people to create and use alternate configuration files, including (but not limited to) alternate color definitions. Let's see, that's 4, or maybe 5, votes for (...) (20 years ago, 10-Aug-04, to lugnet.cad.dev)
|
| | | | |
