It looks like you're new here. If you want to get involved, click one of these buttons!
orxEvent_SendShort(orxEVENT_TYPE_SYSTEM, orxSYSTEM_EVENT_CLOSE)
The application will still quit, but I don't know if its safe to do that way. I'm instead trying to set the "quit" input as active, causing the code in the run function to return orxFAILURE and terminate the game. If its still OK to use orxEvent_SendShort, it would still be nice to know how to use this function if I ever get around to adding replays.
Comments
As for orxInput_SetValue(), any value works. It all depends on what you expect when you read it.
If mapped to a physical peripheral, buttons will set the value to 1 and joystick axes will set it to X with -1 <= X <= 1.
But really, you can set it the way you want, it's only a convention between who's setting the value and who's going to read it.
As for SetValue() it means the value will be set for one frame whereas SetPermanentValue() will set it for the given value till someone sets it to something different.