see picture below for the current behaviour. This might be more suitable as Bug report, but i wasn't sure.
I've tried to build a workaround by defining tab as custom-input and managing the order myself. That doesn't work however, since Factorio is "consuming" the tab key, but only in the case of "finding the next element". If no input is focused i received the event and can focus the first element.
Here's my wish list:
- Make the logic skip hidden inputs and focus the next visible input
- Raise the key event, if and only if focus_next() fails
- Let me order input elements to guide the built in logic (in a similar way to prototypes)
- I would like to have the ability to get the current focused element
- tab-key-workings.png (11.65 KiB) Viewed 650 times