We've had some other reports of this behavior, but we haven't seen it ourselves. If you or anybody else in this forum is still seeing the problem, I'd like to pursue this further in a private discussion and see if you can help us investigate the problem.
John Fultz email@example.com User Interface Group Wolfram Research, Inc.
On Dec 3, 2012, at 3:03 AM, Gordon Robertson <firstname.lastname@example.org> wrote:
> > On OS X, variable colours are now behaving as they did in v8. I've not yet > identified which conditions give me the awkward always-blue variables and which give the current blue-to-black behaviour. (I'd crashed v9 and restarted it, and reopened the notebook that I'd been working on.) > > Gordon > > On 2012-12-02, at 1:03 PM, Gordon Robertson wrote: > > In v8 (on OS X), the name of a variable that did not have a value assigned was blue, and it changed to black when a value had been assigned to it. This was simple and very handy. > > After a day of using v9, all user-defined variables seem to be blue, period. > > Preferences | Appearance | Other offers 'Global symbols that had no value assigned' as blue by default. But if I type in and execute something simple like: aVariable=2, the variable name is blue before and after I've assigned it the value 2. > > I'd prefer to have a distinct colour for variable with no value assigned. Am I missing something simple? Apologies if I am. > > Gordon > -- > Gordon Robertson > Michael Smith Genome Sciences Centre > BC Cancer Agency > Vancouver BC Canada > www.bcgsc.ca<http://www.bcgsc.ca/>