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
--
