Subject:
|
Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Wed, 11 Feb 2004 20:10:34 GMT
|
Viewed:
|
3631 times
|
| |
|
|
In lugnet.cad.dev, Michael Lachmann wrote:
> The idea with environment variables is not bad, though there are two major
> disadvantages against the methode implemented in MLCad (which uses some ini
> file entries to define the search path, including an option for the user
> wether the entry shell be visible for selection or not):
>
> 1) It doesn't allow to define paths inbetween the standard search paths,
> which is a disadvantage sometime.
> 2) You do not have any chance to hide subparts and primitives from the users
> view.
>
> The implementation in MLCad uses ini file entries (currently MLCad.ini but
> can be in any other file as well here I'm totaly open) and starts with a
> section
> [SCAN_ORDER]
>
> followed by one or more path definitions, each beginning with either HIDE or
> SHOW followed by the path. The path can contain spaces.
> HIDE would make parts found in this path invisible to the user, but include
> it when searching for parts, while SHOW would make the parts in this
> directory visible to the user.
>
> Example:
> HIDE BFC\P
> HIDE BFC\Parts
> HIDE P
> SHOW Parts
> SHOW MODELS
> SHOW MODELS\TEST
>
> When looking for a part, MLCad will take the part first found going through
> the directory list from top to bottom, other parts with same name in later
> directories will be ignored. This mechanism allows the definition of
> unofficial parts in a path following the official paths. Once the part
> becomes official, the user would get the correct image without event have to
> take care.
>
> However and whatever comes out, I must say I would be rather disappointed if
> the solution is totaly different from that what I invented and would have
> less outcome for the user than my solution.
I agree, however I'd like to point out that you could have started a
discussion here, before inventing your own personal solution. That's
what this forum is for.
Getting back to your example, I have some questions. Are all of those
paths relative to the LDRAWDIR? Do you allow absolute paths? Is the
directory containing the model file allowed to be moved around in the
SCAN order? How would you specify that?
Don
|
|
Message has 1 Reply:
 | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
| "Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Hsxs1M.rIC@lugnet.com... <SNIP> (...) Ok right, but when I start discussing new features I'm going to implement there will be a much bigger delay in new MLCad version than we (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
| Hi, Just to give my two cents ... "Lars C. Hassing" <sp.lars@am.hassings.dk> schrieb im Newsbeitrag news:Hsw4I7.MxC@lugnet.com... (...) search paths for parts. (...) usual ones. LDView got its implementation after a preview release of MLCAD 3.01, (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
132 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- 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
|
|
|
|
