 |
Confirmed. Tabbing to the value textbox should not result in the key textbox being changed. |
 |
Resolved. This was caused by the GroupCycle class, which "cycled" the selection even when only 1 item was available for cycling. |
 |
Hm, I'm still getting this, but I know what's up, something I forgot to mention in the original report (sorry) - keybind conflict. I have GroupCycleForward (you do mention GroupCycle) bound to Tab. I've always had it that way, seems natural to me, to tab through the func_static components. Needless to say this doesn't work. Is there a way to capture the Tab when the textboxes have focus and suppress it for groupcycling in that case? If so, great, but it's not terribly important - if not, I guess I'll need to think of a new hotkey. ;) |
|
|
I can confirm this issue, it is indeed related to the TAB being caught by both the EntityInspector as well as the EventManager which routes the event to the GroupCycleForward command. I don't know yet how to resolve this, because GTK is already setup to not forward the key events to the EventManager when it can be used in the foremost window (i.e. EntityInspector). |
|
|
I disabled the keystroke propagation for the GroupDialog now, which should the EntityInspector work as expected. Note that this also affects the TextureBrowser, MediaBrowser and Console - when any of these GroupDialog windows are focussed, keystrokes are not propagated to the main window anymore. |
|
|
Okay, this currently works fine, however: considering the change back in 458, I will have to wait to check this. The hope is that changing 458 back doesn't bring this problem back. If it does, and there is no other way around it, I'd side with the lesser of two evils, that is leaving it so ESC and TAB DO still propagate around, and if the user doesn't like the way it operates, they should change their group cycle key (as I have, to shift-Tab). And in that case, perhaps the default should change as well. ESC to clear selection is important. Normal Tab functionality among textboxes is important. These things are fundamental to standard UIs even if they conflict in this case with some DR-specific function. |
- Anonymous
