I have 2 way comm's going with Girder.
The first is Girder to Xlobby. Every button has an Event code associated with it. There are standard ones in the installation document. Make sure you use those (makes life alot easier!). All the others must be assigned a numeric code. I started a 100 for the main screen, 120 for the Album list, etc.
In Girder, learn your remote code associated with a command. The action of the command will be
1) Click the Command Tab
2) Select Command from the drop down list
3) enter 55555 in the WParam
4) enter the number you assigned to the button
5) Click apply
6) Click the Taget button
7) Find XLobby in the top list called Running Tasks/Windows and select it (note XLobby must be running). This will populate the Setting section of the window
Uncheck all except for the Executable (should be XLobby2.exe)
9) Click OK
When you press the remote button, it sends the event to Girder, which in turns sends a message to XLobby to activate that button.
To get XLobby to send a message to Girder, follow the instructions in the Install doc. Why do this ..... good question.
In my case, I have the Application groups (ie CDex, TT, etc) disable, but have the App started commands in another group. When you press TT Start from the remote, I enable the TT Group and disable TT Start command. This prevents 2 copies of TT from running. If I click on TT button in XLobby, I must tell Girder that TT is to be started and arrange the groups as required. Girder actually does all the work, it changing resolution, starting TT, enabling the group, disabling the start command, etc.