Developers--
A suggestion:
There is something not quite right about how the buttons named "Default", "OK", and "Cancel" behave in the "Common Settings" window.
First, when the window is first opened, the default button (as opposed to the button named "Default") starts as the button named "Default". This is not conventional and can easily lead to user errors (see below).
Second, when the button named "Default" is clicked (which may actually be the default button--see above), there is no recourse or warning that most current user settings have just been or will be reset. Once it's clicked, user settings are immediately lost. This would not normally be considered "user friendly".
Third, after the window is closed, the default button (as opposed to the button named "Default") floats to whichever button was clicked when the window was last closed within the session. So, when a user opens the "Common Settings" window again, the default button will now be whichever button was clicked last. If the user changes the current navigation choice in the navigation bar, the default button floats back to the button named "Default" again. This floating behavior is also not only unconventional, but it breaks a major paradigm of what one means by a default button or action.
The standard paradigm for a window like this would be to set the default action or button to always be the OK button. Cancel or Default would be optional user choices. Any button that will cause a changes to occur would warn the user that this is about to happen and allow the action to be cancelled, unless there is an additional setting that allows the user to turn those warnings on or off.
It would be nice to see these easy, straightforward, user-supportive enhancements included in a future release.
Regards,
Ed S.
A suggestion:
There is something not quite right about how the buttons named "Default", "OK", and "Cancel" behave in the "Common Settings" window.
First, when the window is first opened, the default button (as opposed to the button named "Default") starts as the button named "Default". This is not conventional and can easily lead to user errors (see below).
Second, when the button named "Default" is clicked (which may actually be the default button--see above), there is no recourse or warning that most current user settings have just been or will be reset. Once it's clicked, user settings are immediately lost. This would not normally be considered "user friendly".
Third, after the window is closed, the default button (as opposed to the button named "Default") floats to whichever button was clicked when the window was last closed within the session. So, when a user opens the "Common Settings" window again, the default button will now be whichever button was clicked last. If the user changes the current navigation choice in the navigation bar, the default button floats back to the button named "Default" again. This floating behavior is also not only unconventional, but it breaks a major paradigm of what one means by a default button or action.
The standard paradigm for a window like this would be to set the default action or button to always be the OK button. Cancel or Default would be optional user choices. Any button that will cause a changes to occur would warn the user that this is about to happen and allow the action to be cancelled, unless there is an additional setting that allows the user to turn those warnings on or off.
It would be nice to see these easy, straightforward, user-supportive enhancements included in a future release.
Regards,
Ed S.