Differences in behavior since upgrade.

[specter333]

I just upgraded to r1030 from 1486. IÔÇÖve been putting it off because I was dreading having to redo all my ir codes. I have EG controlling so many things that it took me a little over an hour, IÔÇÖve become dependant on EG for most everything I do on this computer.

I have questions, not problems, about the upgrade and some changes IÔÇÖve noticed and I havenÔÇÖt found any documentation on whatÔÇÖs new with the update. Perhaps someone can show me where that is.

1. I run a gyration rf remote and keyboard which used to be seen as two different devices. Now it seems to see both of them as one device. It sees some buttons from both devices as the same..

2. This version doesnÔÇÖt seem to be stopping keystrokes from going to other apps like the old version. For instance the mute button on my remote correctly mutes the audio but I used to have it trigger the macro for muting the system and show an on screen display. Now when I push the button it toggles the mute twice, once normally and once through EG. My quick fix which is working just fine was to add a third toggle to get where I want to be.

3. I have a 3D Connections Space Navigator which is like a mouse used to navigate 3d worlds or models. It is seen by EG as another HID device. Version 1486 logged tons of gibberish, nothing I could use for events. Now r1030 sees it a HID device and a joystick and both seem to be giving me useable events in the log. But how can I keep EG from seeing it as two devices. There could be times I would have this and a joystick connected. Edit, I still don't get usable events, the HID plugin logs the same events no matter how I move the device and the joystick plugin locks up when using the device with it. Oh well, it would have been fun to play with.

As I said none of these are really problems, IÔÇÖm just curious if there is a fix in case I do want to change how I use these things.

Thanks for any advice.

Almost forgot, I'm running XP64 SP1 on a intel quadcore system. Much of the weird things I run into, such as EG crashing a lot, I think may be the 64 bit operating system.

[stottle]

1. I run a gyration rf remote and keyboard which used to be seen as two different devices. Now it seems to see both of them as one device. It sees some buttons from both devices as the same..

Bitmonster changed the way decoding was done. He actually cleaned it up so it is a bit more accurate, but he also put some re-mapping directly into the decoders, which I think was a bad idea. Probably what is happening is that you get different codes (keyboard.0x11111111, and remote.0x11111111), but any code 0x11111111 is being turned into Mce.Play which is the only event so see in the log.

2. This version doesnÔÇÖt seem to be stopping keystrokes from going to other apps like the old version. For instance the mute button on my remote correctly mutes the audio but I used to have it trigger the macro for muting the system and show an on screen display. Now when I push the button it toggles the mute twice, once normally and once through EG. My quick fix which is working just fine was to add a third toggle to get where I want to be.

Do you have exclusions that are supposed to be triggered by events that aren't being sent with the new remote codes you are getting? It sounds like one event is triggering multiple actions, including keyboard emulation.

3. I have a 3D Connections Space Navigator which is like a mouse used to navigate 3d worlds or models. It is seen by EG as another HID device. Version 1486 logged tons of gibberish, nothing I could use for events. Now r1030 sees it a HID device and a joystick and both seem to be giving me useable events in the log. But how can I keep EG from seeing it as two devices. There could be times I would have this and a joystick connected. Edit, I still don't get usable events, the HID plugin logs the same events no matter how I move the device and the joystick plugin locks up when using the device with it. Oh well, it would have been fun to play with.

What events are you getting? Also, which plugin does this device use? It should be possible to have this device and a joystick, especially if they use different plugins.

Brett

[specter333]

Bitmonster changed the way decoding was done. He actually cleaned it up so it is a bit more accurate, but he also put some re-mapping directly into the decoders, which I think was a bad idea. Probably what is happening is that you get different codes (keyboard.0x11111111, and remote.0x11111111), but any code 0x11111111 is being turned into Mce.Play which is the only event so see in the log.

That sounds reasonable. Still not a problem for me, I was just wondering what changed.

Do you have exclusions that are supposed to be triggered by events that aren't being sent with the new remote codes you are getting? It sounds like one event is triggering multiple actions, including keyboard emulation.

No exclusions. The more I think about this I think the reason I was using EG for muting in the first place was because the mute button wasn't working directly with windows. Something outside of EG may have changed to allow the mute to work within the OS.

What events are you getting? Also, which plugin does this device use? It should be possible to have this device and a joystick, especially if they use different plugins.

The Space Navigator shows up under the HID plugin and the Joystick plugin. The joystick only showed events left, right, up and down but it crashes EG after just a few events. The HID pluging receives a ton of events, in a form something like SpaceNav 4.05632 but it gets the same events from all six axis so there's no way to use it. It would probably need a plugin of it's own and I'm sure this isn't used by enough people to make it worthwhile.

Thank you for answering my questions.

[specter333]

Ok, the mute thing is becoming a problem because I just figured out that sudden volume jumps I've been getting lately is from the same behavior.

Just like when I push the mute button the OS toggles mute one way then EG toggles it back, the volume controls are being seen by the OS and EG causing large jumps in volume for each key press. However EG still presents the correct OSD for the volume.

I don't see how updating EG caused the OS to start seeing the volume/mute commands so I maybe mistaken that they were not seen before. The OS may have been able to see them but EG blocked them before they got to the OS.

Am I remembering the behavior correctly? Should EG stop the key presses from reaching the OS? This version doesn't seem to.

Thanks again for your help.