I'm trying to figure out how to control tab order in a property grid.
We use a bunch of BoundedFloatTupleEditors for colors, vectors, etc.
Currently, hitting tab moves to the next property rather than the next component of the tuple.
This annoys the pants off a lot of users.
As far as I can tell the critical code is the ProcessDialogKey of the PropertyGridView class.
On tab it does:
Property property = GetNextProperty(SelectedProperty);
...
StartPropertyEdit(property);
Which doesn't move through the Tuple's components but rather to the next property.
A basic solution would be to check whether the current property has more than one component and move to the next one of those, if it exists.
It seems ideal if I could tag properties with meta data telling the PropertyGrid whether a tab should move to the next component OR a different property AND which property/component.
For example, we have other properties for which it would be nice to go to the first tuple component of the next property on tab and THEN jump back to the 2nd tuple component of the previous property and finally the 2nd component of the 2nd property (e.g. Min/Max type fields).
I don't suppose there's any way to achieve this with ATF in its current form?
Thanks for any ideas.
-Len