Keyboard arrow keys with input focus?

Hi, I have this annoying issue whereby if an input has focus the arrow key presses are not detected.

Is there any work around for this? I obviously cant "always" unfocus from inputs, and the having input focus at all times is pretty much mandatory of the app.

Any ideas?

This is obviously quite an isolated issue, but I cant seem to get an answer from anyone so here is a work around for anyone who might one day come across it (which is bizarre as from what I can see in the inspector, it is exactly the same...)

Add in a html element, add the exact same input code (you can even copy and paste it from the "actual" text input element using inspector).

This then allows you access to Document regardless of input focus...

You can then bind keydown using JS and isolate the keydown using keycode.

Andy

This is by design. Other users reported that they didn't want the game controls to function while using form controls (for example it's irritating if game shortcuts and controls are firing while trying to type something in to a text input). If you focus away from the control and back to the game, it will continue using input for the game.

I see, I think when it is designed one way and demand is there for another way, surely its reasonable to make both options available?

Can there not be an option for this on the input object?

Andy

Why would you want this? It seems sensible that you're doing one of either typing in a text input, or controlling a game, but not both at the same time, that seems chaotic.

this proprietary software receives the data and pastes it into what ever has focus.

That sounds like a weird and extremely specific situation. Doesn't it have an API or some other way to get the data without needing to have a focusable text field to automatically paste in to?

It's such a specific situation I doubt we would change Construct to support it even if we were making software dedicated to application development.

It is very specific which I fully understand. I'm not asking you to change it for this case as the work around is working just fine.

I think the point I'm trying to make is; if the software (construct 3) does something (in this case detect key presses when input has focus) and there is a request to change this (in this case to NOT detect if input has focus), make it an option for both scenarios and not just change it the other way.

To answer your question, unfortunately not, it is a laser measurement device that simply sends the data via bluetooth, the proprietary software receives it and "pastes" it, more so for use in Excel.

I guess I could try using the Bluetooth object and receive the data directly..

Will see how I get on.