 | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I agree, and prefer <> around all tags. (...) Ah, but what about leading blanks. ;^) Nevermind, I don't think you can create an absolute path that starts with leading blanks. (...) But wait. The reason given for looking in LDRAWDIR is for a (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) The data contained in either environment variables or ini files should have exactly the same format. (...) Trailing blanks are preserved in both env var and ini files. So I still don't think quotation marks are necessary... (...) I didn't mean (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Where to store the preferences? While I've been aware of this thread, I haven't actually been following it, so correct me if I've got the wrong end of the stick. (...) MacOS 9 and earlier is a single user environment and it was easy to place (and (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Sorry to immediately respond to my own respond to my own reply, but I forgot one minor detail. The corallary to this bit is that to be safe, Windows programs should treat both / and \ as path separators any time they parse paths, and work (...) (21 years ago, 2-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I believe that this isn't entirely true. We had a problem at work where a program didn't work right in Windows 9x (I think it was 98, but I'm not entirely sure), but worked fine in Windows NT and Windows 2000. After some careful debugging, I (...) (21 years ago, 2-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) That's not exactly true. I'm sure you can work out an arrangement with Lars. After all, L3P is not entirely open source, and the benefit of all the LDRAW tools using an identical parts search strategy is probably more useful than having you (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Oh. I didn't know it was as easy as: ~/MacOSX/environment.plist I guess that is one route. In Cocoa, which is what Andrew and I are both developing in now, it is really easy to grab prefs that have a unique name for the application. It isn't (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:HtwMAE.3BM@lugnet.com... (...) Done, sorry about that - but it was a hard day at work :-( (...) As mentioned earlier in this thread ... we should go with: 1) Users Home (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Ok I hop on again ... "Lars C. Hassing" <sp.lars@am.hassings.dk> schrieb im Newsbeitrag news:Htnz7B.G2z@lugnet.com... (...) located (...) directories, (...) (URL) However, I suggest section name [LDrawSearch] which is more in line with [LDraw]. I (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Actually Environment variables work pretty well on OS X because they've set up a standard place to put them, and it's one of those plist files. See here for details. (URL) would be nice though to have a standard fallback location for the (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
