Problem with KEY_SNAPSHOT

Scarabol · Post by **Scarabol** » Thu Dec 10, 2009 2:39 pm

Hi,

the Key-Code for the Screenshot Button should be KEY_SNAPSHOT, right?

Im using MastEventReceiver

long tmp = event.KeyInput.key;
// debug tmp -> tmp = 44 or 2c in hex, which is KEY_SNAPSHOT in keycodes.h

Code: Select all

if (receiver.keyPressed(KEY_SNAPSHOT))
printf("doesnt work");
if (receiver.keyPressed(KEY_KEY_A))
pritnf("works well");

Whats gone wrong?

MfG
Scarabol

Mel · Post by **Mel** » Thu Dec 10, 2009 4:50 pm

Not necesarilly, although maybe there is a key named like that you can use ANY key to grab a snapshot. Take a peek to the Demo source, as it has an snapshot system integrated in it. Its key is the F9, for instance.

Scarabol · Post by **Scarabol** » Thu Dec 10, 2009 5:38 pm

Well i'm sorry i dont want ANY key i want THIS key...

MfG
Scarabol

CuteAlien · Post by **CuteAlien** » Thu Dec 10, 2009 8:05 pm

You probably want KEY_PRINT. I don't know what the SNAPSHOT key does - according to MS documentation it is for "PRINT SCREEN key for Windows 3.0 and later", but my print screen key does just send PRINT and not SNAPSHOT events.

Scarabol · Post by **Scarabol** » Thu Dec 10, 2009 9:03 pm

Print has no effect, too.

Pls try it for yourself just use example 16 Quake Map Shader with another key code for Key_F9 and send me your results.

I tried:
F9 - works well
Print - nothing happens
Snapshot - nothing happens

MfG
Scarabol

CuteAlien · Post by **CuteAlien** » Thu Dec 10, 2009 9:23 pm

Hm, I can only test on linux right now, but maybe it's the same. It seem the key-down message is never received by the application - only the key-up. Not sure right now why that is the case and if it's avoidable. Usually it's not a good idea to use system-keys for application behaviour, so maybe just switch to another key.

Scarabol · Post by **Scarabol** » Sat Dec 12, 2009 6:02 am

Hi,

key-down message never reach my eventreceiver...
key-up message do???

Seems to be a ....... BUG!!!!! RED ALERT!

MfG
Scarabol

CuteAlien · Post by **CuteAlien** » Sat Dec 12, 2009 6:15 am

Well, I guess we can't pass on messages which we don't get and we do not filter that message out. So it seems like the OS does already filter that message, not much we can do there.

Scarabol · Post by **Scarabol** » Sun Dec 20, 2009 7:54 pm

How do Irrlicht get the key states?

GetAsyncKeyState(#VK_SNAPSHOT) works well on my system...

MfG
Scarabol

CuteAlien · Post by **CuteAlien** » Sun Dec 20, 2009 8:02 pm

Irrlicht does pass on the system messsages WM_KEYDOWN and WM_SYSKEYDOWN. VK_SNAPSHOT is not delivered with those. The alternative would be installing a key-hook. We might do that maybe (for other reasons) at some time. You are certainly free to use GetAsyncKeyState to find out the current state.