Different colors per user

[Kenneth Brody]

Quoting Joe Chasan (Thu, 21 Feb 2008 07:38:08 -0500):

> On Thu, Feb 21, 2008 at 01:25:04AM -0500, Kenneth Brody wrote:
[...]
>> Under Unix, $MenuNormal and $MENUNORMAL are two distinct environment
>> variables.  Under Windows, %MenuNormal% and %MENUNORMAL% are one and
>> the same.  As such, your above getenv() will return the environment
>> variables as you describe above.
>>
>> Note that config variables are not case sensitive.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> What does this mean specifically?  That variables set in fp's config file
> are not case sensitive, or any fp-specific variables set anywhere (including
> shell) are not case sensitive?

Sorry if I wasn't clear.  I meant that "variables set in filePro's config
file are not case sensitive".

So, under Unix, setting PFQUAL in the environment is different from setting
PFQual in the environment.  Under Windows, both PFQUAL and PFQual are the
same environment variable.

However, in the filePro config file, both PFQUAL and PFQual are the same,
regardless of platform.

> It appears from this incident that only the former is true and if
> so, the help files should show the variables in their correctly (e.g
> globally and non os-dependent) accepted case - but of course this
> brings up look 'n feel issue question of why are all non-color variables
> in caps and color ones require Mixed Case?

Umm... A non-optimal design decision made when 3.0 added the config file,
which at the time did not include environment variables?  (Note how the
TextNormal/TextInverse entries are at the bottom, following a "Colors:"
label.)

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com