08-30-2016 09:39 AM - edited 08-30-2016 09:58 AM
In reference to implementing the solution at:
Operators will hold the tab key to tab faster. Holding the key tab results in a very fast change in focus on controls; focus appears to be changing in an erratic order, i.e., not in the tabbing order that was set up for the controls. Not usable as-is.
How can the Windows tab sequence be slowed down to provide repeated, reliable tabbing?
I could abandon tabbing and use a KeyDown event: for example, using up/down arrow keys to shift focus to adjacent controls, with some logic to make exceptions for the controls at the applicable index boundaries.
Thanks,
Solved! Go to Solution.
08-30-2016 09:58 AM
08-30-2016 10:25 AM
Sounds like you didn't setup the tabbing order as you expected otherwise the tabbing order erratic issue should not persist. The default order is by creation of controls on the FP.
Changing the windows setting slows down the all the keyboard entries.
As you mentioned there are other events that can be used, mouse over, mouse up 1 left click, mouse up 2 right click etc. I can see this easily implemented for all boolean since the events once fired issue the reference to the control. From there you can change the boolean properties.
Rich J
08-30-2016 11:25 AM
@GerdW wrote:Hi,
you could decrease the key repeat rate in the Windows settings…
Thanks. That fixed it.
08-30-2016 11:30 AM
The tabbing order was as I had set it. Tabbing was so fast that it appeared that only 3 out of about 25 controls were ever in focus.
Setting Windows 'key repeat' slower (in Win 7, I set the keyboard to the slowest possible key repeat rate) allows the operator to see all the controls as they're highlighted and in the expected sequence.
Thanks,