Girder & Intel Wireless Gamepad

[Mark F]

I don't have this hardware nor application so this may not help at all.

Have you tried using the "clicked" command under the "window" tab (far left) of Girder rather than the "space" command under the "keyboard" tab?

You can target this at a spcific window (a button is a window too) by pressing the target button (this opens a targetting dialog) and dragging the crosshair in the upper right corner to the target button.

I hope this helps.

[Chris Carollo]

I've almost got my whole Home Theater PC automated so that I can just use the gamepad for everything, from startup to shutdown. When at the desktop, different buttons start different DVD players in different modes (anamorphic/letterbox with YXY). It's great. Almost.

The problem I'm running into is dealing with Intel's crappy gamepad profile activation system. As far as I can tell, the only way to activate a profile is to use their app, and then either do a bunch of keyboard commands to put the selection over the "Activate" button -- which of course when pressed brings up a the dialog for editing the profile (um, no, I just wanted to activate it, thanks).

Right now I have Girder spoofing a bunch of keypresses to activate the profile and then quitting the app, and detecting when the profile editing app fires up and closing it. It all works fine, except that all my keyboard events are being passed to the topmost app, rather than to a specific app. So there are timing issues, depending on what else is going on -- I suspect that certain key events are going to the wrong app.

Unfortunately, I can't seem to get any keyboard events passed directly to the profile activation app. They apparently do nothing. So I guess my questions are:

1. Is there any better way of activating a gamepad profile than using Intel's hateful software?

2. How do I send a keyboard command to an app? Do I need to specify the proper child?

3. How do I determine which child maps to which part of the dialog? The profile activation app has 30+ children, none of which have names (there's an Afx window and 20+ Button windows). If I could just send a Space keyboard event to the proper button, I wouldn't have to do all the up events to move the selection over it first, which would simplify things.

I'm so close to having it perfect. Any help is much appreciated!

[Chris Carollo]

Ooh, that sounds good. I'll try it out tonight.

Thanks!