May be the good way to mix the two is having the config windows displaying the envar if defined instead of the value in config. In that case it should be greyed out with a little information message explaining why. So user will not get confused changing something without effect, and it remains consistent with the regular unix behaviour.
Le 20/04/2016 10:04, Mário Luzeiro a écrit :
Hi Cirilo, Thinking as a regular user perspective, I vote for "WYSIWYG", i.e: the one defined in the GUI. Users will get puzzled if something that they don't see is change the variable path. Mario ________________________________________ From: Kicad-developers [[email protected]] on behalf of Cirilo Bernardo [[email protected]] Sent: 20 April 2016 01:19 To: KiCad Developers Subject: [Kicad-developers] 3D filename resolution 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 : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
