Tab order for components
planned
c
clint.banzet
It would be great to be able to specify a tab order for components on a screen. Power users would benefit greatly from not having to use the mouse on a data entry intensive screen. For example, I just converted a Microsoft Access app to Ignition, and although the users love the new app, they sorely miss being able to tab between data entry fields.
Log In
m
michal.koblasa
This is a very essential feature for web forms and very easy to add. This is a must must-have.
Y
Yousuf Nejati
planned
J
James Caudle
A tab order for Vision would be nice as well.
s
stieu
This would be a great feature for the Perspective Module.
s
sanderd17
See also this forum thread: https://forum.inductiveautomation.com/t/tab-order-of-input-components/767
I agree with Carl Gould that the VB way of doing things is horrible, and should not be copied. But a hybrid solution is possible.
It would be possible to add a "tabIndex" property, similar to VB. But the first difference should be in the default value. Defaulting to the input order makes no sense. Instead, all input components could default to a constant "1".
After that, the current algorithm (left to right; top to bottom) can still be used for all components with the same tabIndex.
This will keep the default behaviour, but allow to customize screens where deep customization is needed (presumably only a few screens per project where data input is very important).
It's also easier to set the tab index than in VB: you can select a group of elements that you want to be tabbed later, and assign the same tab index to it. Then the internal algorithm can determine the logical order inside that group.
Bonus: tabIndex 0 could be used to skip tabbing to it.