girder events

[birty]

how do you learn girder events such as "GirderOpen" ?

[Ron]

Note: I overhauled the event editor for tomorrows release so this description is not acurate for your release.

Open the event editor, select 'Girder Event' in the Event Device combobox. The Event String combobox is now filled with the Girder events, select the appropriate event.

Also I don't think there is a GirderOpen at the moment, tomorrows release has it though.

[quixote]

I started a new GML to do a couple of test and found that it was in fact my keyboard input that is not being accepted by Girder. Actually, that is not an accurate statement. Let me correct that. Girder sees my keystrokes, but does not register them properly in the event editor. For instance, in a a test GML I used simple OSD to Say "this is a test", then I added an event and went to the edit screen. I chose keyboard from the drop-down (though detect active source worked as well) and then tried to learn the keystroke, but the learn button is greyed out. If I click on the input box and hit the "T" key, it only enters a t in the box (duh), the dropdown for the key did not contain the code for the key and in the end the only way I could get it to work was open the logger window and look at the code, then type it in manually. So, in short, the keyboard is understood by Girder because I can see all of the codes in the logger, but there is something wrong with the event editor.

Also, I'm almost sure that this is why my old GML will not work correctly. Looking at my imported GML, I notice that in the General box on the left that the key codes are all different from the key codes that I get in the logger when I press the appropriate keys.
An example would be for "Fan Mode" I have used the key F (of course). Now in the imported GML, when I click on that event I see that it is for the keyboard driver and directly above that I see the code 4600000. when I hit the key F and look in the logger I see the code 21000000 (up) and 21000000 (down).

[Ron]

were you using keyboard ex before?

[quixote]

Was keyboard ex to stop keys from being sent to the OS? If so, yes I was, but only for a few commands. I used the keyboard driver plugin that was written by you, Ron.

I tried deleting my old event strings for a couple of my commands and re-creating them and it doesn't still doesn't work.

[Ron]

That is funny because I didn't change the keyboard driver.

[quixote]

I have no clue what the problem is. It seems like I've tried everything. I have both dropdowns set to raw:keyboard. I figured out how to learn the keypress, but it's not too intuitive. I liked it better in 3.3 where you just hit "Learn" and it automatically fills in the code when you hit the key. I have managed to learn keys and execute the command, but it is very finicky and doesn't work sometimes. Can you give me some tests to try and I will report the results to you? I don't know what to look for anymore to help. Thanks.

[Ron]

I wish I knew what to say, but here I am not having trouble with events not firing. If you could send me the GML with the part that works and sometimes doesn't I'll have another look at it.

[quixote]

I have to go to bed now (I have work in about 8 hours), but if you look at the GML I sent you, you should be able to hit control with ` and it should activate "enable Mode Change". This enables the group just below it after "mode change disable" called "Mode Change". Hitting the same keys should disable the group.
The only way I was able to get it to work (sporadically) was by using a key such as z instead. I could not get the states to work, though.

[quixote]

I find it hard to believe that I am the only one with this difficulty. I guess I should mention that I am using a logitech wireless keyboard, but I don't really see how that could be the problem. The logger shows the keystrokes without fail.
I don't need to de-install Girder 3.3, do I? What plugins can I and should I copy into my Girder4 directory?

[Ron]

I am sure you are not the only one. I currently am focussed on the other bug (set volume thread). After that I'll get back to this one.

[quixote]

Ok. Thanks. Sorry to be a pain. :oops:
I can't do much testing without being able to use my keyboard commands. Just let me know whenever you're done. I know you have a lot on your plate right now.

[JSMain]

I'm having trouble too!

I tried to learn an event last eve, and it sees the keyboard, but doesn't recognize the command.
Either this isn't as simple as before, or something has changed. It not as simple as "learn event", and go on as it used to be....

What am I missing?

[birty]

right click on the action you want to assign to an event, click on add event, right click on the new event and select edit, press detect source and then press the button you would like to use, the event string drop down list should now only have one event select it. an alternative method is to activate the logger and just drag an event from the log to an action