|
A GUI should have RICH controls, and should be able to be navigated by the keyboard as WELL as the mouse - not either/or.
In the end, if a user's dominant function is mousing, then the mouse should be in the dominant hand, and the keyboard in the non-dominant hand. If the keyboard is the dominant function, then the mouse should be in the non-dominant hand. In this case, if you key with your right hand and mouse with your left, you don't have to switch. How amazing is it that thinking a little differently might stop the whining?? :-)
And then there are the companies who think Solitaire should be removed. Like Evan said, that is a management issue. Solitaire is the best mouse training tool...
----- Original Message ----- From: <GKern@xxxxxxxxxxxxxxxx>
Subject: Re: The Perpetual Myth of iSeries Obsolescence
My main gripe about GUI designs is that they have you move from keyboard... to mouse... to keyboard... to mouse... wasted motion!"That's a peeve of mine too." Exactly - especially when I begin typing, and then look at the field (on a browser) and see nothing was input. Then I (again) have to reach for the mouse, move it to the field and click inside the field to enable the field as input capable. You'd think tabbing to the field would make it input capable. Clearly not head's down friendly. That's a 'feature' that's not modern by my definition. Regards, Jerry
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.