Bureaucrats, emailconfirmed
1,221
edits
→Modeless Design
| Line 294: | Line 294: | ||
==Modeless Design== | ==Modeless Design== | ||
Everybody knows about the problems "modes" create though you may never heard about this term. But for sure you already had trouble with the Caps-Lock-Key that changes the rESULT oF tYPING. If you push the Caps-Lock you enter a mode. This means that: | |||
* The same actions cause different results now | |||
* You attention is not necessary directed on the status of the mode, which means it can be triggered and used unnoticed. | |||
If an application behaves strange and you actions have results you did not expect it is likely that you entered a mode. If you are lucky you notice it and know how to get out of this. If not - which is foar more often the case - you mess up your work, loose data and think the application in corrupt.It is but not its functionality but the design! | |||
One of the rare examples of modes that don't cause confusion are the tools in image editing applications. They introduce modes too, because a mouse click will cause a selection (using the select tool), painting (brush) or deleting something (eraser) But it does not cause problems because we know the tool-modes from the real world, we have direct feedback and the cursor changes as well. So we are aware of the mode. | |||
Very often you encounter modal dialogs. They pop up in front of your main window and block the interaction with it. So clicking the main window will have a different result that usual and it is: nothing. This is especially bad if the modal window just is a notification that something worked or not. | |||
Modes should be avoided. E.g. introducing a navigation mode- and editing mode will just confuse your users. Make the different functions available without the demand to enter a mode. If there is no way to avoid a mode, indicate clearly and visible that the mode is triggered and how the user can escape the mode. | |||
=Get to know if your ideas work!= | =Get to know if your ideas work!= | ||