- Posts: 29
- Joined: Mon Apr 03, 2017 6:46 am
Sun May 13, 2018 10:09 pm
This is already around for some time.
When it comes to GUI design, pressing the Tab-key takes you to the next field to change a value (or not).
In for instance the Inspector's Transform, I usually change the scale and position of an item (to create the staion-ID).
Now I click in the Zoom X and change the value and press Tab to accept it.
Pressing Tab takes me to the Zoom Y which I don't change.
Now, logically wise, pressing Tab should take me to the next field, Position X. But, I don't know where it goes at first, but after 4 Tab-presses, the focus is finally on the Position X. That is not how it should work though
I should note that this happens in plenty more areas, where pressing Tab doesn't take the focus to the next logical field, but somewhere... whereever.
Maybe someone could review all this, to make the program slightly more RSI-friendly?
When it comes to GUI design, pressing the Tab-key takes you to the next field to change a value (or not).
In for instance the Inspector's Transform, I usually change the scale and position of an item (to create the staion-ID).
Now I click in the Zoom X and change the value and press Tab to accept it.
Pressing Tab takes me to the Zoom Y which I don't change.
Now, logically wise, pressing Tab should take me to the next field, Position X. But, I don't know where it goes at first, but after 4 Tab-presses, the focus is finally on the Position X. That is not how it should work though
I should note that this happens in plenty more areas, where pressing Tab doesn't take the focus to the next logical field, but somewhere... whereever.
Maybe someone could review all this, to make the program slightly more RSI-friendly?
