#1 is the sanest option, it would be nice if there was an indication
in the editing dialog that there's a global override when you
view/edit them. Something like coloring them red and putting a warning
message in the bottom of the dialog like Settings marked in red are
currently overridden by
Le 23/03/2015 22:44, Garth Corral a écrit :
It seems like option #1 is the saner option.
If I’m understanding the change, once the variables are edited they
become configuration variables. Typical precedence for configuration
is usually something like, command line - environment - local
It seems like option #1 is the saner option.
If I’m understanding the change, once the variables are edited they become
configuration variables. Typical precedence for configuration is usually
something like, command line - environment - local config files - global
config files, from highest
#1 works slightly better for normal users for OS X, if I'm understanding
you correctly.
Adam Wolf
Cofounder and Engineer
WL
On Mon, Mar 23, 2015 at 1:36 PM, Wayne Stambaugh stambau...@gmail.com
wrote:
I'm getting close to finishing up the environment variable editing
dialog and I'm struggling
I'm getting close to finishing up the environment variable editing
dialog and I'm struggling with the best option to set variables that
have already been define outside the currently running process. Here
are the options that I see:
1) Set all environment variables to the values defined in the
It should work better for users on all platforms except if they have
already set the environment variables externally (as we ask them to do
before I added the default settings or they used one of the kicad source
build and install scripts) and they forget to remove them before using
the new
6 matches
Mail list logo
