kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 4/20/2016 8:27 AM, Nick Østergaard wrote:
> 
> Den 20/04/2016 14.16 skrev "Wayne Stambaugh" <stambaughw@xxxxxxxxx
> <mailto:stambaughw@xxxxxxxxx>>:
>>
>> Mario,
>>
>> That's not going to happen.  I specifically designed the environment
>> variable behavior for development purposes.  That's why the environment
>> variables defined externally to kicad take precedence.  This allows me
>> to keep my test libraries separate from my normal working libraries.
>> This allows me to do:
>>
>> export KISYSMOD=/path/to/test/footprint/libraries
>> pcbnew
>>
>> which is really useful for debugging and testing.  Entries in the
>> environment variable configuration table in kicad are highlighted in
>> grey to inform the user that a given variable was defined externally.
> 
> So does it show the external env var or the config one? If it shows the
> external one, that is what Mario expects.

The internally defined environment variable is shown.  I suppose I can
show the external one and make the greyed out table entries read only so
they cannot be edited but that may be confusing as well.

> 
>> We even have a help dialog that explains this which if I am not mistaken
>> is the *only* help button provided by any dialog in kicad.  On clean
>> installs this should not be an issue because it's highly unlikely that
>> users will have any of environment variable defined that are used by
> kicad.
>>
>> Wayne
>>
>> On 4/20/2016 4:04 AM, Mário Luzeiro wrote:
>> > 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
> [kicad-developers-bounces+mrluzeiro=ua.pt@xxxxxxxxxxxxxxxxxxx
> <mailto:ua.pt@xxxxxxxxxxxxxxxxxxx>] on behalf of Cirilo Bernardo
> [cirilo.bernardo@xxxxxxxxx <mailto:cirilo.bernardo@xxxxxxxxx>]
>> > 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     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>