> I am not sure how Jmol was behaving in the past... but I imagine this
> design handy:
> 1. the preferences are the boot settings... i.e. the values the
> several rendering options when Jmol is started...
> 2. we should define a list of options that the users is likely to
> change within one Jmol session. These should have menu items, the
> others not... The option values toggled with the menu do not alter the
> preference settings, which only indicate the startup values
> Not sure if I make myself perfectly clear... but anyway, here is a
> second try:
> 1. For labeling, shading, etc, both menu and preferences exist...
> The preferences define the boot settings and the initial menu
> settings... In the Jmol session itself the menu settings do not
> change the boot setting, but change only the current working
> settings... Changing the preferences changes the boot settings and the
> current working settings.
> 2. antialiasing, etc only occur in the preference dialog and determine
> both the boot settings and the current working settings...
> Did this help?
I agree with you.
And that is the goal that I was trying to work on.
But I was unable to figure out a scheme to update the values in the menu
system ... so I was frustrated.
After I have settled down and thought about it for a day or two I will go
back and try again.