Subject:
|
Re: Bug in L3PAO when path deleted/renamed
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Mon, 23 Oct 2000 18:31:41 GMT
|
Viewed:
|
1113 times
|
| |
|
|
In lugnet.cad, Daniel Crichton writes:
>
> 'Now model path should be full if not in standard paths, or shortened if it
> is
> Dan
yep, that would work.. i just put in a massive boolean if-then to check before
the command line generation routine kicks in...
the problem isn't checking the paths, the problem is knowing the location of
ldraw. if you have LDAO in place, it's easy.
Looks like i'll need to drop in a locator diolag box to look for the ldraw.exe
(just like i do for the l3p.exe) if the path isn't found in the ldraw.ini
J
|
|
Message has 2 Replies:
 | | Re: Bug in L3PAO when path deleted/renamed
|
| "Jeff Boen" <onyx@flash.net> wrote in message news:G2wBGt.EG4@lugnet.com... (...) of (...) ldraw.exe (...) That would be great, just like MLCad operates. You could also look for the LDRAW_DIR environment variable (I think that's right) that the L3P (...) (24 years ago, 23-Oct-00, to lugnet.cad)
| | | Re: Bug in L3PAO when path deleted/renamed
|
| (...) It's better to look for ledit.exe, so you don't accidently find the ldraw.exe download/installation file. LDAO used to get caught on that one frequently. The startup code was happy, because the path in ldraw.ini pointed to a directory (...) (24 years ago, 24-Oct-00, to lugnet.cad)
|
Message is in Reply To:
| | Re: Bug in L3PAO when path deleted/renamed
|
| "Jeff Boen" <onyx@flash.net> wrote in message news:G2w4LD.H1C@lugnet.com... (...) with (...) default (...) easy (...) Can't you just loop through the standard dirs and do something like this? 'Read model dir and filename from (...) (24 years ago, 23-Oct-00, to lugnet.cad)
|
20 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
