How do i know which keys I used?

[Ron]

Hmm,.. there is not real list of that in Girder, but you can check if you assigned a key by pressing it while girder is in the foreground and looking if the treeview jumps to a new key,.. that would be an indication that you have assigned it to that key.

[Ron]

Hi Yvon, i'm guessing that they will be the same on any machine, just post a few code + meaning and see what the other users think. If this is the case i can make an translation table in the plugin.

-Ron

[Ron]

Yvon forgot his password so i am posting this for him:

RealMagic remote ;
Play button gives 1ee0e0f8e0f8
Rewind gives 1ee0f8f8f8f8
Ok button 1ee018f818f8

Now if anyone could confirm these are the same for all of you i can collect them and create a translation table.

[Ron]

I'm aware that there seems to be a bug in the keyboard driver but until now I nor anyone else has been able to find it. I'll upload the source again for your reading pleasure, the more eyes on the source the less bugs.

[Ron]

Aaaaaaaaah!!!!! Thats it, and i was wondering why i didn't see this bug, i don't have a wireless keyboard so i see all the events,... I'll see if I can fix this little pesky bug! That is if windows can tell me if the ALT is not pressed any longer,.. if windows cannot then we are out of luck

-Ron

<font size=-1>[ This Message was edited by: RonB on 2001-05-24 09:12 ]</font>

[Ron]

I'm using GetAsyncKeyState() now, this *should* poll the device instead of rely on the Window messages. At least that is who i interpret the Win32 API,.. i'll release this updated keyboard plugin in a few moments, if you would be so kind to test it!

-Ron

[Ron]

I didn't get around to checking this problem, i'll get back to you tomorrow.

[Ron]

Nope no progress really. The stuck ALT an Control is a Airboard problem. If the transmission fails at the moment when you let go of the alt key windows never gets the WM_KEYUP event, thus making it stuck. I tried to implement a fix for it but that one broke a lot of other stuff so i reverted to the older plugin. If anyone has time to dive into this problem feel free to do so. Also the new (alternative) keyboard plugin seems to work good under win2k.

[Ron]

http://www.girder.nl/download.php?Link=150

The keyboard Ex 2.1

-Ron

[Ron]

oops :roll:. I've uploaded the original keyboard source code. Have fun.

-Ron

[SteveV]

maysken,

Keep in mind that begining with version 3.0.23, Ron added a comments field (located below the "Antirepeat wait time [ms]" field) which should allow you to note which remote key was used for each command. IMO it should be much easier to identify the command based on written comments versus trying to find a match to a hex string.

Regards -- Steve

[Yvonus]

Same remark for me. I should have done it earlier. Now I'm maintaining a text file on my desktop with my "IR planning" so that I know what input events (being from keyboard or realmagic remote) are already used.

The "ir code" is good for debugging, but for sure it would look nicer to have, at least, the plugin the event comes from (keyboard, IrDA, etc..), and, if possible, the key it match.

"Realmagic remote - left arrow" would look nicer than "14574768768627EF" :wink:

Ron, I guess the codes are "stable" (I mean they don't change from one machine to anothre) for the keyboard (including the webboard "<whaterver>Z" special codes). I can
try to make a list of existing codes for the RealMagic but will those be the same on any machine ?

Let me know what you think Ron.

[Yvonus]

Found back my password :wink:

As told yesterday evening to Ron, other codes are already known ;

The webboard multimedia keys (thanks to Vladimir), cover codes from 700000Z to 7B0000Z I think.

Keyboard should be the same for everyone. space bar is 200000 if my memory is correct.

Of course, this can be done with input devices for which we know all possible incoming codes. Keyboard, realmagic remote are some of those. IRman on the other hand will eat almost any IR code coming to it. No way we can figure out that you're using an old Philips tv remote to control your pc :wink:

However, we can think of leaving an open door for people who would like to add more entries to the translation table.

For instance ..

156ef783de "My Philips remote ; play buton"

Will help for sure poeple figuring out, afterwards, what input event triggers an action.

[Yvonus]

May I suggest you to take a look at an AVScience thread http://www.avsforum.com/ubb/Forum12/HTML/010705.html

Hindif is using an Airboard Ir keyboard with Girder and he doesn't get the same code for a given key everytime.


For example, it will recognize the key "p" as IR code "A0000XC", and later it will see "A00000C"

[mflaster]

I'd just like to point out/suggest, as I did in the AVScience thread, that it sounds like your airboard receiver saw an alt-down, but did not see an alt-up. I don't think this is a bug in girder, but rather I think somehow the Airboard receiver is picking up a stray alt-down, without the alt-up, and so (eventually) when you hit a key, the modifier is applied to it.

Is it possible that some IR code one of your remotes sends is the same as the <alt-down> frequency for the Airboard?

Mike


Mike

[mflaster]

But try this test. Hold down the alt key. While you're still holding it down, block the IR output from the Airboard. Then release the alt key.

Now type any key. It will be modified with 'alt'.

I know this is true, because this is the way I programmed my Pronto to send things like ctrl-alt-a.

The point is, pushing and releasing the <alt> (or any modifier) actually sends *2* IR codes to the Airboard receiver - down and up. (Actually, I guess this is probably true for all keys.) If it misses the up, or if some other device sends a code which is similar to Alt-down, then the keyboard handler/OS/whatever will *correctly* treat the next character typed as being modified by <alt>.

Mike

[jediperry]

I get the same values, although I always assumed that the above play button was actualy the slow-mo button. I never tried the sigmah drivers, and the symbols could be either way round.:smile:

Mike

<font size=-1>[ This Message was edited by: jediperry on 2001-05-22 01:06 ]</font>

[bwana]

When you press 'learn event' then Girder learns to associate the programmed event with the incoming keypress. A hex code is displayed in LED. But what if i forgot what keys i have pressed for other events? You know, i dont want to assign the same key to 2 different things. Is there a way to generate a list of all keypresses used?

[hindif]

yes, I'm having a problem where Girder seems to misinterpret IR codes after an arbitrary amount of time. I've read of others having a similar problem when Girder was minimized/maximized.

I'm using the keyboard plugin for Girder, an Airboard and Win2K. I've noticed that when Girder misinterprets the IR code, it sometimes sees the keycode as if the "Alt" key or "Control" key is pressed as well. Here's an example:

When I press the "CD" button, Girder sees it correctly as 7000X0 and runs the associated action. Later, Girder will see the code as 700AX0, which is the IR code if I hit the "Alt" button along with "CD". I'm pretty sure the Airboard isn't sending the wrong code because I programmed my Yamaha remote to send the correct code. When Girder gets confused, it misinterprets the code from the Yamaha remote as well.

Any suggestions?

[hindif]

that would be great, thanks. i'll try to take a look at it. if i can run any tests for you, please let me know.

[hindif]

thanks for the suggestion. I just did a little test and basically confirmed that the "alt" key doesn't work that way. Basically, if I press Alt, then release it, then press a key, I get the same IR code for that key as if I never pressed Alt. If I hold Alt down and press the key together, I get a different IR code. So, the Alt and Control keys don't have any effect unless they're pressed along with another key at the same time.

[hindif]

thanks Ron and mflaster. I will definitely try this as soon as I get home!

[hindif]

Well, I'm seeing "different" behavior using the new keyboard driver as well. Here are the codes recognized when hitting the "CD" button on the Airboard:

Girder v.3.0.22, keyboard.dll v.2: 250000Z
Girder v.3.0.22, keyboard.dll v.1: 25000XZ
Girder v.3.0.15, keyboard.dll v.1: 25000X

One problem is that the code for the left arrow is also 250000Z in the first two and 250000 in the last.

Usine the 2.0 version of keyboard.dll, I do see that Girder recognizes the IR code for just the alt key when it's pressed, but I'm not sure if that fixes the problem. Please let me know what else I can test.

thanks!

[JayGuerette]

On 2001-05-23 18:54, RonB wrote:
I'm aware that there seems to be a bug in the keyboard driver but until now I nor anyone else has been able to find it. I'll upload the source again for your reading pleasure, the more eyes on the source the less bugs.


I didn't see it, did you post it?

[JayGuerette]

On 2001-09-22 19:18, RonB wrote:
http://www.girder.nl/download.php?Link=150

The keyboard Ex 2.1


I had meant the source... :razz:

[maysken]

Would you like for users of all other remotes to send in a list of the codes generated from those remotes so that you can continue with the plan to build a listing of what each button on each remote sends...in order to be able to tell what button is linked to a command, and if it's already been used for another?

[maysken]

Thanks Steve,
I had no idea that was what that space was for! It's not labeled as such.

Thanks again!

[apai]

but how come I get a different hex code for the same remote button that I click on. My receiver is a built-in infrared device.

[tjheikki]

Any progress here?

Hadn't looked at this thread but now I understand why I couldn't use the extra keys with my newbuilt machine (I guess 3.22 was new then, upgraded that too..:smile:

My girder also (3.22-3.24p3) receives same codes for the extra keys and normal ones which was not the case with the old machine using 3.1x so now I have had to keep turning on the monitor to use things the old-fashioned way.

I have sometimes also seen the stuck alt/control problem, I think that also came with some version later than 3.00 (might be also something else I changed). The keys are not stuck in the AirBoard receiver as it seems that any non-modifier key-up action releases any pending modifiers so any missed alt-up would be fixed after one misintepreted key. Actually I use that feature with the Pronto all the time; I have only key down parts of modifier key codes programmed and let the following printables reset those modifiers. Also, everything works OK everywhere outside Girder.