1) When would one use mjextman.exe in the file field (OS tab) as opposed to the full file path (C:\WINDOWS\system32\mjextman.exe)? I've also noticed another exe file in the Media Center directory. When would that be used, if ever?
I don't know.
I generally use the short form, but I've read of cases where the Windows executable path gets messed up, so Girder can't find the mjextman file. Also, if JRiver decides to change the location of that file, using the long form will neccessitate a lot of changes to GMLs.
2) What are the advantages of using the command line format over the Windows Messages approach? Is the same command/parameter format used in both cases?
The same command/parameter is used. Some people like helper programs, others don't. It's a matter of personal preference. Again, using Windows Messages may minimize the number of changes needed should something change with the helper program.
3) In the DevZone document I see references to MCCs such as MCC_PLAY_PAUSE but the Girder gml file in MC 10 uses /MCC 10000, 0 in the Step Size field. Which is correct?
The DevZone document references the full names of the commands. The actual parameters that get passed are all numeric. It's just we poor humans that need names to go with those numbers.
4) I would like to program my MX-500 to emulate keyboard strokes such as up, down, enter, etc. and I know you can do that in the Girder Keyboard tab. Do I need any input data in the OS tab in order to navigate the menu in Theater Mode? I noticed that the MCC list included a keyboard section (MCC_KEYSTROKE, 27000) and have wondered if that needs to be incorportated in the command. In other words, how does Girder know how to interface with MC Theater Mode unless there is some reference to the executable in the OS tab or elsewhere?
Make sure you check out the Girder website's "Getting Started" document. You'll find that the various tabe that you are referring to are called "Action Tabs". They are all mutually exclusive--meaning if you assign a Keyboard action to a Girder command, you cannot assign an OS action to the same Girder command.
What you are interested in is the "Targeting" dialog box that exists in several of the action tabs. This dialog box allows you to specify which application on your machine will receive the Girder command triggered by your eventstring.
I'm going by memory here, so be gentle! For example, Create a command in Girder & name it "Up". Then, choose the keyboard action tab and select the "Up" action from the special key drop down menu. Make sure you click the "Apply" button to save the action. Finally, choose the target button to specify which application you want to send it to. It will help if MC is already running. Since you are interested in working in Theater Mode, you can check the box that says, send to "Foreground App". That means the Girder command you named "Up" will be sent to whatever app you have frontmost at the time.
Finally, you'll need to assign the eventstring to the command you created. In the Main Girder window, click the "Learn" button, then press the button on your remote you want to trigger the Girder command. If you have your IR receiver setup correctly, Girder will learn a coded form of your IR signal.
Basically I'm looking for an overview of how the executable should be configured, in order to be controlled by Girder, and how the parameters should be incorporated into that process. It's probably clear to you guys but I can't seem to find this information in one place. I've picked up pieces here and there but need someone to help me pull it all together. Hopefully others will benefit from the answers to my questions. Thanks for your patience!
Let us know if you need more help!
Best,
Brad
Author
Topic: Girder Basics (Read 1158 times)