| | 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)
|