Bureaucrats, emailconfirmed
1,221
edits
IFD:Course Interaction Design (view source)
Revision as of 08:37, 9 September 2011
, 9 September 2011→Modeless Design
| Line 322: | Line 322: | ||
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. | 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. | ||
Besides of modes there are other conditions that can cause errors and problems. The following chapter will explain more. | Besides of modes there are other conditions that can cause errors and problems. The following chapter will explain more. | ||
====Refereces==== | |||
*Jeff Raskin's [http://opac.ub.uni-weimar.de/DB=1/SET=1/TTL=1/SHW?FRST=1 "The Humane Interface"] has a lot of information on Modes and Modeless Design. | |||
===Preventing Errors and Dealing with them=== | ===Preventing Errors and Dealing with them=== | ||