I'm trying to intercept the Ctrl/Chr key on a full QWERTY Nokia device (E71). It seems like the keyPress event isn't generated for this particular key.
Any ideas?
There is a good chance that this key is only a keycode modifier.
You can probably only see whether it is pressed at the same time as another one.
It would not exactly but the first key to not trigger a Canvas.keyPressed() callback on a phone.
Related
recently I bought a wireless keyboard from Lidl:
SilverCrest
IAN 377704_2101 SPCC 2 A1
Model Nr.: HG08233A
Everything works great, but there's some setting that releases the button after it was being pressed for 22 sec. I know it's a time-related setting because I was playing with the key repetition setting and no matter how fast/slow it was typing(repeating the same key over and over), it stopped after 22.XX sec. (measured on my watch, so that's why .XX).
Has someone any idea how to turn that off, so the button stays pressed till I release it? It's making the keyboard useless for gaming.
Filter keys: OFF
Sticky keys: OFF
Toggle keys: OFF
I have one more wireless keyboard from ConnectIt and it doesn't have that issue, so it must be something drivers/settings related.
I wanted to use it as a replacement for my current ConnectIt keyboard, but the purpose is development (which is great for) and gaming (which is impossible due to key releases).
I've tried to look into registry, but I wasn't able to find anything.
Have a nice evening, and thanks for any ideas ;)
In Linux (most distros?) there is a Keyboard Shortcuts settings app that lets you set keyboard shortcuts like the key combination that minimizes a window or switches to the next workspace/desktop or moves to the next media track. I want to connect to the event that is fired when the defined shortcut is pressed rather than the key combination as the key combination can change but the event is always the event. Specifically I want to capture the next/previous workspace/desktop events, not the workspace/desktop changing, but the keyboard request to make the change.
However, I cannot figure out where these events are surfaced. Does anyone know where I might connect to these events? I would think GTK+ has some way to surface it, but even if I have to go down to X11/XLib, I'm ok with that.
Ultimately I will code this in python, but for now I'm just looking for a way to capture these events.
The new keyboard doesn't have keys for media control (the image on Amazon was small). I want to re-purpose the keys for e-mail, sleep, calculator, etc... into media control keys.
This is my keyboard:
Keyboard-Amazon
I've researched AutoHotKey and found that this is possible; however, I am not sure how to fully implement it. I cannot find any way to identify these keys to the program. I would be happy if you could tell me how to identify these keys to the program and how to get it to respond in the correct way. That is, next track and previous track selection.
Autohotkey has built in support for some multimedia keys.
Browser_Back
Browser_Forward
Browser_Refresh
Browser_Stop
Browser_Search
Browser_Favorites
Browser_Home
Volume_Mute
Volume_Down
Volume_Up
Media_Next
Media_Prev
Media_Stop
Media_Play_Pause
Launch_Mail
Launch_Media
Launch_App1
Launch_App2
Use them with a send command, example:
F11::Send,{Media_Play_Pause}
If you keyboard had special keys you will have to consult the documentation on that.
I've read up on the internet about how to simulate keypresses on the keyboard in the X window system. So far, I've got a program, written in C, that works at sending key events from the traditional keys on the keyboard. However, I can't figure out a way to simulate someone pressing the keyboard's mute/volume up/volume down keys.
This may not even be possible to do with the XKeyEvent structure I used for the previous key presses, since I didn't find anything remotely close in the keysymdef.h file, and I think that those events are delivered to the host OS rather than each individual window.
I've also fired up xev and it didn't give me very much helpful output (or at least any that I could decipher).
Does anyone have any tips on where I should look?
Try with keycode 123 keysym 269025043 for volume up (xF86XK_AudioRaiseVolume)
and Keycode 122 keysym 269025041 (xF86XK_AudioLowerVolume), hope that helps
I want to know the type of the mobile keypad programmatically. Is there any way to track this. If yes, Please guide me to get this issue ?
Haven't tried this, so may not work, but try and see.
According to this link, J2ME handsets with QWERTY keyboards "almost always return their corresponding ASCII/UTF8 value [as keyCode parameter when the framework calls Canvas.keyPressed()]". So try calling something like Canvas.getKeyName(65) (i.e. the letter 'A').
If it throws IllegalArgumentException you will know that 65 is not a valid keyCode for that device, therefore it's not a QWERTY handset.
Let me know if it works!