Most of the following words have been transferred from #661.
As introduced in ODOP v4.1, the AutoFix feature can take users by surprise. Specifically, the user is focused on entering a numeric value and does not notice that the action of entering a value has also put that variable in Fixed status. Much later, the user does not get the solution behavior that was expected. Troubleshooting then belatedly discovers that the variable was in Fixed status.
Separately, having AutoFix ON is a troubled default because it leads novice users into over-specified design situations. This raises the priority of drawing user attention to the action of AutoFix.
The objective here is to briefly highlight the action of AutoFix without introducing the need for any additional keystrokes or clicks.
Possibilities include:
a very brief animation of the Fix/Free checkbox
a brief appearance / disappearance of the word "AutoFix" overlayed onto the value field or associated constraint violation fields.
the AutoFix action could place the text "AutoFix" in the constraint violation fields and the next user entry could remove that text.
A first step in the direction of resolving this issue was taken in branch #639 (now closed). A second step was taken in issue #661.
Various conversations have touched on how it might be possible to make it obvious how the user can over-ride the default AutoFix behavior. Ideas include:
a radio button in the currently unused area to the right of the Alerts buttons.
A settings "hamburger" button that invokes an enhanced File : Preferences menu item. This could be placed either in the menu bar or in area to the right of the Alerts buttons
Most of the following words have been transferred from #661.
As introduced in ODOP v4.1, the AutoFix feature can take users by surprise. Specifically, the user is focused on entering a numeric value and does not notice that the action of entering a value has also put that variable in Fixed status. Much later, the user does not get the solution behavior that was expected. Troubleshooting then belatedly discovers that the variable was in Fixed status.
Separately, having AutoFix ON is a troubled default because it leads novice users into over-specified design situations. This raises the priority of drawing user attention to the action of AutoFix.
The objective here is to briefly highlight the action of AutoFix without introducing the need for any additional keystrokes or clicks.
Possibilities include:
There are multiple websites and YouTube videos describing bootstrap animations and React-Bootstrap transitions. For example: https://react-bootstrap.github.io/utilities/transitions/ https://mdbootstrap.com/docs/standard/content-styles/animations/
A first step in the direction of resolving this issue was taken in branch #639 (now closed). A second step was taken in issue #661.
Various conversations have touched on how it might be possible to make it obvious how the user can over-ride the default AutoFix behavior. Ideas include: