| |
In lugnet.cad.dev, Don Heyse wrote:
> But wait. The reason given for looking in LDRAWDIR is for a central
> networked LDRAW installation at a school. It'd be nice to have a
> default ldraw.ini file at the central location that can be overridden
> by one in a users home directory.
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
|
|
| |
In lugnet.cad.dev, Don Heyse wrote:
> 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.
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 format used on the platform it is running.
/Lars
|
|
|
