I’m allowing my users to use keys to navigate in videos (e.g: left arrow to go backward in video or right arrow to go forward in video)
we use the window’s API in order to get the user’s input for these actions (it has nothing to do with the game, so overwolf.games.inputTracking won’t be helpful)
while trying to reuse a desktop window as an in-game window, I’ve found a discrepancy between desktop and in-game in window functionality (again, native window object, nothing special here)
@shir.brass from my tests, I can see that it always returns code: Hyper, for desktop and in-game windows. I don’t know the reason. I can forward it to R&D.
But the question is - isn’t the key is not enough for you?
“is it enough” is a tricky quesiton…
is it enough for implementing my solution? it could be, yes.
is it enough so OW will support the standard? I don’t think so
my expectation is that a window’s KeyboardEvent would work like a KeyboardEvent, that’s all
@shir.brass yes, of course, my meaning was more like - do you have a workaround for now… as fixing it probably will be in low priority and will take some time.
I believe that our API should resolve it. It’s just a matter of priorities.