I’d love to see grid view editing navigation improved.
Repro: Bring up a “Property Set assign properties” action and select a property set with multiple fields. Select the “Set Property Values” box and move around with the cursor keys. Put the cursor on a value field and type a new value. Now it’s no longer possible to move around in the grid.
Expected: I’d expect return to start editing the line below, or tab/ctrl+tab to move to the next grid field. Perhaps ctrl+cursor to move to another field.
Actual: Tab moves to the “Ok” button below the box. Left/right moves in the active text box, but no other movement keys will do anything. The only way to edit another field is to tab out and back (tab, shift+tab), move to the next field and start typing.
Note: To be honest I haven’t tested all available grid editors, but assuming you use the same code everywhere it’s probably something that would be beneficial elsewhere as well.
Thanks
Andreas
Andreas,
Thanks for bringing this to our attention.
We have had a recent issue with one of the grid controls we were using (a bug with rendering certain controls in the grids) which has made us change the behaviour of certain grids to be different to work-around this issue. Once we’ve got a fix for this, hopefully we can improve the usability and consistency of the grids.
cheers,
tate.
Hi, just an update on the issue, running on 5.0.52, I tend to get a lot of lost input as I finish editing a field and then press ok, but since I didn’t move the focus from the box I edited before I pressed ok, the data is never stored and thus lost. Also, one uses return to complete variable lookups, while IMO tab would be more appropriate.
Some concrete examples:
1. Add a variable to be passed to an included script. Edit the variable name and move to the value field, type something and press ok (mouse). The value is lost.
2. Enter %SomeVar and press tab. The field is lost.
/axl