armitage

Hi, Sice the applications that I ran with G keys were allways launched to the screen where the ckb was opened, I made a patch that looks the selected screen (the screen where the mouse is) and launches the application to that screen. I tried to do it with Qt, but it wasn't possible to determine which screen is selected with Qt (http://stackoverflow.com/questions/32040202/qt-5-get-the-mouse-position-in-a-screen/32045873) so I finally choosed to make it with libX11. I could share the patch if you're interested on that feature, so you can add it to the master branch of the ckb. Another comment I wanted to make: when you run an application with a G key, it's not possible to run the same application again. It might be a bad thing if you want, for example, open a terminal with a G key. Since you can open lots of terms, it would be interesting to allow to launch the application as many times as you want. I removed that behavior in code (because it's not useful to me) but I think that it could be a good decision to allow the user to configure that behavior in the key binding configuration. Thank you very much for that driver, it's great :).

Hi, I'm having some issues with ckb and multihead. Since ckb depends on qt, I decided to use KDE4, and I configured it to use awesome as window manager. In order to keep the awesome desktop and design I disabled Plasma and KRunner. The problem is that the ckb can only be loaded at one DISPLAY, and when you push a G key, the application will only be oppened on the screen when the ckb was ran. But if your mouse cursor is at the other screen, you'd expect the application to be opened at the screen where the mouse is. Does someone has the same issue? Since the mouse's cursor current display can be readed by code, I think that the solution could be to set the DISPLAY variable with the mouse value before launching the application, and the application will be opened at the screen where the mouse cursor is. I made the change on keyaction.cpp, but I'm having issues while compiling the source (my first ckb installation was from portage, not directly from source, and I'm probably missing something).

Forgot my post, I found the options on the ckb. Sorry for the poor research before asking.

I forgot to mention, I'm using Gentoo GNU/Linux, and I use Awesome as window manager.

Hi, I've installed the driver, which works very well in general. Good job!! :) However, it seems that G keys doesn't work for me. I tried to get the key codes for G keys with the evtest command, and I get no codes when I push a G key. I can see all the key codes for all the keys but for G keys, it's like they're ignored. I was expecting to get the key codes, since the first page of that thread says that the G keys works. I says that advanced macros don't, but that's not what I want. I just want to get the keycodes. My idea is to run a specific command when a specific key code is detected (that's what I was doing until now with the K90 keyboard). I also tried to read the keycodes with the http://sourceforge.net/projects/keytouch/files/ application, without any luck. Could you help me to get that? Does someone have the same issue? The main difference between the K95 and K90 that I can see, is that the K90 had 2 different input devices (/dev/input/event6 and /dev/input/event7) but the K95 has only one (/dev/input/event6). On the K90, the G keys where readed from event7 and the "normal" keyboard from the event6. Since the K95 has only the event6, I understand that I must read everything from the event6 (but it doesn't seem hat event6 populates the G keys codes). Maybe I'm reading from the wrong device? On /dev/input/ckb0/* and /dev/input/ckb1/* I don't see any device to be readed that could provide the key codes. Thank you in advance for your help, Daniel. PS: I'm sorry for my bad english, if I wasn't clear enough on some point, please feel free to ask. I wrote it my best, but english is not my native language.