Bo Peng wrote:
The alternative would be to remove _all_ toggling in the dialog. I am
not sure it is needed.
Maybe on a different topic, I propose that we find someway to merge
apply and save to OK. They kind of confuse me... Other applictions
usully keep a list of 'applicable' changes and 'need-restart' changes,
and tells the user the app needs to be restarted to make some changes
available, only when these 'need-restart' changes are made.
Bo
First, regarding JMarc's comment, I use toggling (of bold face) rather
extensively. Usually I'm turning it on, but sometimes I'm turning it
off (because I copied bold text but don't want the copy bold, or because
I bolded the end of a line and forgot that this would make subsequent
text bold, or just as a result of a change of heart).
Second, regarding Bo's comment, we may be confounding a couple of things
here. There are places were we definitely need to keep Apply and Save
separate, as the former applies the change only to the current session
and the latter preserves it after restarts. (This is different from
requiring a restart to take effect, which is a separate issue. There
are changes in the options dialogs -- I think path changes fall into
this category -- that do not take effect until a restart, and it's
possibly a bit confusing to users when this happens, as their first
inclination is to think the change was not recorded. It would be nice
is there were a status message indicating a restart was required.)
As far as the Ok button, I generally take this (in any package) to mean
"changes have been recorded/applied and the dialog is done". In
instances such as the converter dialog, where you might want to enter
multiple changes at one time and apply them as you go (lest they somehow
be lost), I think both Apply and Ok are needed (as well as Save to
separate temporary from permanent changes).
My 4 cents (2 cents per issue). :-)
/Paul
