On-keyboard LCD support. Details within.

GenKreton · Posted: Tue Jan 02, 2007 7:34 am Post subject:

I have spent the better part of today collecting and sifting through the data about the g15 keyboard. Some of it is quite old and the various changes in the tools made ti a tad difficult. However, I do have most things working and I spent time fixing up the gentoo-wiki page on it. The information and structure still needs a lot of work but it can greatly help people who are just buying on of these keyboards. I invite everyone else to also help fix it up since many of you have spent more time on this.

A few notes, the amarok script will not work for me but all of the lcdproc scripts I have tried work great! All of the macro keys are working inside my KDE, but unfortunately I cannot get them to function inside of the two games I tested them in. perhaps the game is not letting the keystrokes get to xbindkeys, I cannot be sure since I know too little about this.

rbu · Posted: Tue Jan 02, 2007 10:36 am Post subject:

GenKreton · Posted: Tue Jan 02, 2007 10:22 pm Post subject:

I posted about this in the other major g15 thread where the amarok script was of discussion. Basically I get an error where it tries to call print() on a filehandle it says is closed. This appears very strange to me since I see it being called to be opened in the code. As per the instructions of the maintainer on the Ubuntu forums, while he was trying to help other people, not me, I downloaded the SVN version but that did not help me either. The output log is spammed with this, and only this error, but the line numbers change to refer to every line printing to PIPE.

rbu · Posted: Tue Jan 02, 2007 10:34 pm Post subject:

GenKreton: Did you only update the amarok script or the whole of g15composer from svn?
Maybe this is a result of bug #158321. Please check whether upgrading to g15composer-3.1 fixes this for you. And don't forget to set the user running amarok in the conf.d.

If it does not help, please file a bug.

GenKreton · Posted: Tue Jan 02, 2007 10:58 pm Post subject:

Alright, thank you. I only grabbed the script from SVN. I just synced and saw the new g15composer today so I will try it! The lcd is working great with all that said. I feel ready enough to start writing a few little screens for lcdproc or g15composer myself. It seems a bit more productive to make them for lcdproc if I ever do anything worthy of sharing.

Now I just need to figure out why my keys aren't being passed to my games. I have only tried enemy-territory and I will try others later. The macros for my CAD program are amazing - an incredible time saver.

It seems that ET might be taking the key, not knowing what to do, and dropping it instead of letting xbindkeys handle it and then ET interpreting the results. The LCD keys and the G1 key (options for lcdproc) both work so there MUST be a way to ensure xbindkeys gets it and passes it to the active application like it should be. Any ideas?

GenKreton · Posted: Wed Jan 03, 2007 7:16 am Post subject:

I am still getting the errors. This entire block is what is repeated in the script manager's error window for the script: