KeyboardAPI

native TriggerRegisterKeyEvent takes trigger whichTrigger, integer eventtype returns nothing
native GetTriggerKey takes nothing returns integer
native SetKeyBlock takes integer i, boolean doBlock returns nothing
native ForceKeyDown takes integer key returns nothing
native ForceKeyUp takes integer key returns nothing
native ForceKeyType takes integer key returns nothing

// constants
constant integer EVENT_KEYUP = 0
constant integer EVENT_KEYDOWN = 1

Tutorial: N/A
Download: N/A
Native Set Type: Single Player or WarSoc
Release: 0.10
Other: N/A

So this basically adds events which can detect any key press instead of just up/down/left/right/Esc?

Yes, and allows blocking and forcing keys too.

Oh sweet. I could actually have a use for this.

*Runs off to install and revamp entire campaign (as usual)*

The only way to use this natives is installing RtC, right? Isn't there any other way to detect any key pressed and released than installing RtC?Unit abilities may detect some keys when pressed yet not when released, is JASS able to do such?

BTW I've been reading about the WarSoc Project and it just rules.

Question: how fast are these compared to the regular keyboard press events?

Originally Posted by Gox

The only way to use this natives is installing RtC, right? Isn't there any other way to detect any key pressed and released than installing RtC?Unit abilities may detect some keys when pressed yet not when released, is JASS able to do such?

BTW I've been reading about the WarSoc Project and it just rules.

There's no way in regular wc3 to do what these native does, except for detecting arrow keys, and ofcourse the way with detecting abilities, which doesn't work very well.

Originally Posted by Pyritie

Question: how fast are these compared to the regular keyboard press events?

I haven't done any speed tests, but since these work around some of warcraft III's safety things, i would guess this one is faster.

Thanks, then I'll try to make this natives work with RtC.

Can you post an example of a trigger using the detection of a key? for example "W". Please, it's kinda confusioning.

library Test initializer Init
    private function Actions takes nothing returns nothing
        if(GetTriggerKey() == 87) then
            call BJDebugMsg("W was pressed")
        else
            call BJDebugMsg("Keycode " + I2S(GetTriggerKey()) + " was pressed")
        endif
    endfunction

    private function Init takes nothing returns nothing
     local trigger trig = CreateTrigger()
        call TriggerAddAction(trig, function Actions)
        call TriggerRegisterKeyEvent(trig, 1)
    endfunction
endlibrary

This is off the top of my head, since i'm at school atm. Basicly, call TriggerRegisterKeyEvent(trig, 1) detects when i press a key, and GetTriggerKey() returns what key it is, as an integer value.

Is the integer value the character's ASCII value?

Well, for characters you can look up the upper case letters on a ASCII table, but other than that, then it's a no. It's a keyboard value. Next release will likely include an KeyboardKey2Char or something, to help this process :)

Also note that, if I'm not mistaking, the current stable version does not support disabled triggers and conditions. It's also not recommended to destroy triggers. Preview purposes only, next version will have a fix for this stuff.

How do I know the right integer for each key button?

The easiest way is to use the example code i wrote, and just try. Look at the message appearing on the screen, and then you'll know which key is which. That's how i do it.