kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

The intended behavior should be to have the envvar always override as
far as I understand Wayne's design decision. I like that. If the
configure paths dialog should show the one from config or the envvar I
am not so sure about. I think it should show the external envvar in
the case that is defined, overriding the one in the config. This
should also aid in confirming that one have set it outside. Although I
sort of think it is bad that the current behavior is that it will only
use the envvar  if the path exists. (This was the case with the
KISYS3DMOD).

2016-04-20 2:19 GMT+02:00 Cirilo Bernardo <cirilo.bernardo@xxxxxxxxx>:
> Hi folks,
>
>  I'm cleaning up the new 3D filename resolution code, removing some
> redundant code and fixing corner-case bugs which break with legacy
> behavior. I'd just like some input on one item: if a ENV_VAR path has
> been defined via "Preferences->Configure Paths" and that ENV_VAR
> already exists on the system, which one has preference? For most
> UNIX applications the behavior is to use the ENV_VAR defined within
> the shell rather than the locally defined values.
>
> - Cirilo
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>