Hi Lee,
A compromise solution may be possible if there is a single screen that
is used for most of the raw data entry, as in someone sits on this one
screen and enters data for many records without having to go to other
layouts/screens. Update this screen with a specific order for doing the
data entry and commit record/go to next new record. Then leave the rest
of the application as is.
If there is no such screen, then I would agree with you, trying to
redesign the whole system is probably to difficult.
There is one other thing, when I did the research study, the only GUI
systems in large use where Mac OS < X, Windows 3.1 and
Unix/Linux/Solaris. Most major data entry systems where green
screen/mainframe for things like insurance companies etc. DOS was still
the main PC operating system without windows. The point to this is that
now everyone uses GUI systems. Not only on their computer, but even on
their cell phone. So trying to train a new employee to not reach for
the mouse may be a bit harder then it used to be. This may be helpful
when you talk to your client.
All the best.
Bruce
On 1/9/11 5:48 AM, Lee wrote:
Thank you all for your comments. I did look at the tab order option
today but its all too difficult, just where do you place the scripted
buttons in the 'tab' order.
The solution used has a variety of screens where some fields may not
require data to be entered. which means the user would be required to
tab through all fields to get to the command buttons.
All too hard I think and not realistic. My suggestion will be to live
with the mouse.
I also believe tabbing through the scripted buttons could potentially
cause the wrong script button to be selected, more so than using the
mouse to click on a scripted button.
Lee
On 9/01/11 6:15 PM, Bruce Herbach wrote:
Hi Lee,
I think the key would be setting the tab order. If you can move from field to
button by using the tab key and then hit enter or start typing to fill in a
field it should work.
Many years ago I was involved in a research project that tested which was
faster for data input, mouse and keyboard or just keyboard. Just keyboard was
much more efficient, at least in the tests we did at the time. Since then GUI
interfaces have improved a great deal, but I believe that keeping your fingers
on the keyboard is still faster..
Hope this is helpful.
Bruce Herbach
Sent from my iPad
On Jan 8, 2011, at 3:04 PM, Lee<[email protected]> wrote:
Hi,
I've had a request from a client using one of my solutions. Can it be used
without a mouse, that is, can key strokes be used to replace the mouse ?
I've never thought about it before so I'm just throwing it out there to see if
its possible.
I guess it just means can you activate scripts from a keyboard instead of using
the mouse to click on buttons.
They're using FM 8.5v2
Lee
--
