A curious problem with orxInput_HasNewStatus(). As I understand it, it should notice a mode change, so that if a key is pressed, it should trigger, and being held has no further effect.
Therefore, orxInput_IsActive("SomeKey") && orxInput_HasNewStatus("SomeKey") should trigger in a callback if the key "SomeKey" is pressed but not held.
I have used the 06_Sound tutorial of a good example to show what could be a potential bug.
Compiling this tutorial on Windows XP under VS2005, when I press the space key which puts some colour FX on the soldier, I have the press the space key very quickly many times to register a key hit. I presume because I have to trip both an "on" and "off" event during the life of the callback method.
However, head over to the linux binary of 06_Sound and pressing the space key is completely normal.
Didn't want to log this into the bug subforum in case it turns out to be a comping option I might have set in VS2005 that might be causing this.
This effect is also observed in my own project.
But the crazy thing is, if the project is a standalone one, and I move the keyboard code to the Run() callback. It is perfect. Isn't that odd?
iarwain, or anyone, have I discovered a bug here?