| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Yes, as Lars said earlier: (...) [LDraw] BaseDirectory=C:\LDraw LgeoDirectory=C:\L2P LdrawSearch="<HIDE>C...MyPrims\In Work| C:\LDrawXtra\MyParts\In Work| <MODELDIR>|<HIDE><LD...BFC\PARTS| <HIDE><P>|<PARTS>|<M...arts\Done" I like the single (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Hi Don, "Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Ht8vwM.ps2@lugnet.com... (...) <SNIP> > (...) Have you ever tried to pull out a variable under MS-Windows with a length of 500 characters? Or what would happen if the (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Something similar (but probably not identical to) the above would have my vote (I'll explain below). I would clarify that if ldraw.ini can't be found in the user's home directory (aka the user profile directory), then the Windows directory (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Right. In case the variable gets too long we can resort to multiple variables: [LDraw] BaseDirectory=C:\LDraw LgeoDirectory=C:\L2P LdrawSearch01=<HIDE>...MyPrims\In Work LdrawSearch02=C:\LDr...MyParts\In Work LdrawSearch03=<MODELDIR> (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) In DOS/Windows the problem with environment space is (I believe) more a problem of limited total environment space. I don't think there's additional limitations on individual variables. So using multiple environment variables might conceivably (...) (21 years ago, 18-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) ME and the NT variants store the environment in the registry so this would only make things worse for 95 and 98. That said, I'd still prefer to keep things short for the environment version of this. One variable, with as many shortcuts as (...) (21 years ago, 18-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:HtAD4n.BCJ@lugnet.com... <SNIP> (...) <SNIP> (...) FILE:// style is fully machine dependend as well, so there is no need to put file in front, but I'm open to additionaly (...) (21 years ago, 18-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) [snip] (...) This could be addressed by prepending each value/line with 1=, 2=, 3=, etc. Steve (21 years ago, 19-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Steve Bliss" <steve.bliss@earthlink.net> schrieb im Newsbeitrag news:mna930t5n6agvkl...4ax.com... (...) etc. (...) Good idea, so how about [LDRAW_SEARCH] 1=SHOW <MODELDIR> 2=HIDE <LDRAWDIR>P 3=SHOW <LDRAWDIR>Parts 4=SHOW <LDRAWDIR>Models . . . (...) (21 years ago, 24-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) It looks good to me. --Travis Cobbs (21 years ago, 24-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) It works for me too. So we should check the user's home directory for an ldraw.ini file containing an [LDRAW_SEARCH] section, then if not found look in the ldraw.ini file in Windows directory. For myself, because of platform portability (...) (21 years ago, 25-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Me too. I think it is a good idea with a separate section for the search directories, it allows shorter keys than suggested in (URL) I suggest section name [LDrawSearch] which is more in line with [LDraw]. (...) Yes, first (...) (21 years ago, 25-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I also considered suggesting [LDrawSearch] but I held back and went with the "me too". I do like [LDrawSearch] better though. (...) Sure, but use lowercase ldraw.ini please! I'm too lazy to remember to use the shift key on a case sensitive (...) (21 years ago, 26-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) OK. (...) But you don't declare LDRAWDIR as C:\LDraw\, i.e. with a trailing backslash. We also use %WINDIR%\ldraw.ini and not %WINDIR%ldraw.ini. I think most variable substitution in any (script) language uses explicit delimiters in stead of (...) (21 years ago, 26-Feb-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Exactly, and you don't look for a part named "\3006.DAT" in the PARTS directory? When you combine the full path to the PARTS directory with the part filename you have to add the "\" yourself, right? So I know you can do it... (...) Ah, but (...) (21 years ago, 26-Feb-04, to lugnet.cad.dev)
|
|
| | 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) Oh yeah. One other thing about an ldraw.ini located on a central server. I'd prefer to leave the client OS up to the user. This reinforces my case for the <LDRAWDIR>parts path format without the nasty OS specific slash character. Enjoy, Don (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Hu0CMF.1Fyv@lugnet.com... (...) Ok, agreed too. So with have <HIDE> and optionally <SHOW> - right? (...) I would still like the quotation marks as an option - not a must. If a (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Lars C. Hassing" <sp.lars@am.hassings.dk> schrieb im Newsbeitrag news:Htz996.1H4@lugnet.com... (...) style of (...) it - (...) What I said ;-) <SNIP> (...) env (...) with (...) notified (...) all programs. (...) That sound interesting - any way I (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) No, but leading blanks would be preserved as well... (...) Isn't that what %ALLUSERSPROFILE% is for? (...) LDRAWINI is just an opportunity for quickly temporarily using another specific ldraw.ini file. /Lars (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) It's no problem handling the \ or /'s. We do that all the time already in our parts referencing e.g. S\3039S01.DAT, we do manage to find the subpart on unix too :-) My library reads env vars and ini files in any format and converts it to the (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Sure. (...) OK. (...) Fine. (...) I think so too. Users will also have the option to use the new app LDrawSetup, which can setup LDrawDir, SearchDirs, LgeoDirectory, MIME-types. /Lars (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) You're welcome. I chose C rather than C++ because L3P is still also compiled with 1988 TurboC. L3Lab and LDrawSetup is C++, but can easily interface to a lib in C. You can write a wrapper class if you think it's necessary. (...) But of course (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I'm logged onto an NT domain right now at work and it's set to this: ALLUSERSPROFILE=C:\Documents and Settings\All Users That's on the local drive. But I suppose you're right, a competent administrator could set it up somewhere on the network. (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Seems to me programs need the ability to specify the LDRAWINI directory (and possibly LDRAWDIR) on the command line, for non-standard setups. Maybe the library needs an Ldraw-specific getopt[1] function as well. ROSCO [1] (URL) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I'm not sure what you're trying to say. Do you mean "USERS need the ability to specify", or "programs need the ability to READ"? Either way, that approach is for advanced users (software geeks) only. We're trying to improve things for ordinary (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) And I'm pretty sure on Mac OS X, if you use the finder to activate your program, you have no control whatsoever over the command line. So you already need another way if you want to click on a LDR file or link and have something happen. Don (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Well to be usable, both must be implemented. (...) As I said it would only be for non-standard setups. I think the Lars' search list is ample for the vast majority of people. Those using networks, etc, probably would classify as "advanced (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Ok, I can see where I myself might use this in a pinch because I almost always run things from the command prompt. However, even I would rather set an environment variable or use some other global setting in an ini file. Why? Because if I use (...) (21 years ago, 4-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Well I don't know how mac command lines work but I was thinking along these lines: Windoze: xxx.exe /LDRAWDIR=C:\LDRAW /LDRAWINI=\\LDRAW_BOX\INI Unix: xxx --ldrawdir ${HOME}/ldraw --ldrawini /etc/ldraw You might also wanna provide old single (...) (21 years ago, 5-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Ross Crawford" <rosscraw@bigpond.net.au> schrieb im Newsbeitrag news:Hu4L6M.1Eyo@lugnet.com... <SNIP> (...) these (...) in some cases "xxx.exe /LDRAWDIR=C:/LDRAW /LDRAWINI=\\LDRAW_BOX/INI will work too. There is no standard function set in windows (...) (21 years ago, 6-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Mac OS 9 does not have a command line. That OS is a dinosaur. You can think of Mac OS X as a decendant of BSD, with a Mac OS 9 look-a-like window server. In fact, you can remove Apple's window server and add X11, turning Mac OS X into just (...) (21 years ago, 6-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) [snip] (...) Again, I'm not talking about most users - most will be covered by the search paths proposed earlier in the thread. This would only be for non-standard installations, where the people installing WOULD be likely to know what I am (...) (21 years ago, 6-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Right. I actually manage 350 Macs and I tried to put LDraw on them and ran into several problems that I had to take up with the Mac developers. So anything that makes this easier for admins is good in my opinion. (21 years ago, 6-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) rofl. I think this qualifies as quote of the day. Steve (21 years ago, 9-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Ok, so maybe there was a bit of irony, considering Mac OS X's roots are much older than 9's. But the lack of pre-emptive multiprocessing, protected memory, and other more evolved stuff does make OS 9 a dinosaur. Apple's washed their hands of (...) (21 years ago, 9-Mar-04, to lugnet.cad.dev)
|
|
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Directory separators were added in DOS 2, which accepted both / and \ for that purpose. The feature was imitated from Unix. At the time, there also appeared a config.sys setting for *switch* character, which would default to / but could be set (...) (20 years ago, 15-Jul-04, to lugnet.cad.dev)
|