 | | Re: In dev: new ldconfig.ldr file
|
|
(...) Yeah, I could see a section in LDRAW.INI like: [Configurations] 0=ldconfig.ldr 1=ldcfgalt.ldr ... (...) Well, yeah -- but then there'd have to be another interface element to allow the user to select the colorblock. I think it would be easier (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) How about a ldcfgblk.ldr? For those of us who prefer to edit on a black background instead of a paper white one? I suppose the software could just swap edge=0 for edge=8 and vice versa, but what about the non-black and white edges? -Kyle (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Yes, I like it. However, is it different from the way we decided to number the search paths? Last I remember, we decided to stick them in the generic [LDraw] section and number them like this. [LDraw] LdrawSearch01=<HIDE>...MyPrims\In Work (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Actually, if ldcfgalt.ldr contains the ldlite colors it should work quite nicely on a black background. After all, ldraw used a black background, and the ldlite colors were based on it. And to be totally honest, the default ldlite edge color (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Err, I missed that point in the search path discussion - or I would have recommended putting them in a different section. If [configurations] is too generic, then how about [LDraw.configurations]? Steve (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) 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
|
|
(...) 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
|
|
(...) Why would you recommend that? My current ldraw.ini is loaded with search paths in the [LDraw] section. I'd say it's the other stuff that doesn't belong there. [LDraw] BaseDirectory=C:\ldraw Convert=c:\lcad\software\im (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) If you mean the Launcher, LDAO Modeler, and Minifig Modeler keys -- those are old. The current version of LDAO stores these keys in the [LDraw Add-On] section. (...) To me, a dot looks more like a delimiter than a space. It somewhat indicates (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Ah ha! I thought I saw some duplicates in there. Then the only thing left in [LDraw] is the various paths to find things. I like that. (...) Ok, so how about this? [LDraw.Configurations] # FILE Config Name LOCALE 0=ldconfig.ldr default EN (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Isn't "LDraw." redundant? It is, after all, the ldraw.ini file. --Travis Cobbs (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Maybe so, but I still like it. :^) Besides, it's really all about backwards compatibility. You're not suggesting we rename the [LDraw] key to [] are you? After all, it's just as redundant. Perhaps I'm a dummy, but I've got all sorts of LDAO (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Multiple ldconfig files really needed?
|
|
(...) Me too, but then again, is there really any need for more than two color setups? With this solution, you'll have to change all your alternative ldconfig files when a new color is added. I think just one ldconfig.ldr file would be an advantage. (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) 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
|
|
(...) <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
|
|
(...) 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)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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)
|
