Context Sensitive Hotkeys? (PowerMate related)

I'm trying to setup my Griffin PowerMate to work with RR in a "touch wheel" like setup. Ive got the scrolling part working in the audio player and browser, but I cannot get the "click" to work in both. Using the KeyTBL.ini I can get one or the other with the "browse" and "play" commands, but I cant seem to get both to work.

I've tried to search for info on this and come up empty...

The most obvious solution I can think of is to have KeyTBL.ini be able to specify different commands depending on the context of the hotkey use.

If anybody has any suggestions, please leave them here....

foltster

I'm assuming you're trying to map the same key (say XX key code for instance) to perform different functions in the audio player and on the audio browser... basically you need something like this in KeyTBL.INI:

XX,"PLAY",audio_player.skin
XX,"BROWSE",audio_browser.skin

This will make the same key perform different functions on the screens above... now, there's no way to make the same key perform two different commands in the audio browser (if that was your question)... but you'd need at least a few different commands to be able to fully browse through the folders and select what you want.. UP, DOWN, Browse folder, Go back and Select/Play...

Does anyone know if this info is still true in the current version of RideRunner? I looked at the KEYTBL.INI file and there are no commas after any of the hotkey commands.

Here's what I'm trying to accomplish: I have a monitor with several "hot keys." There's a program from the manufacturer that maps these monitor hot keys to keyboard presses. What I'd like to be able to do is have these keys function as radio presets when I'm on the radio screen, and perform other functions when I'm in the Nav screen, or on the main screen. If the information in the posts above is still relevant, then it sounds like I just need to figure out the name of each screen where I want specific hot keys. Presumably, if a specific screen (skin) filename is not indicated, then the hot key is global.

Have I got that right and does it work as I described? Anyone else tried this?

This is still valid and your assumptions are correct - if you don't add the last part (comma+skin name) it just means the hotkeys are "global". What you're describing is the exact purpose for this keytbl.ini file. The skin name is just the file name for the screen in question (i.e. radio_player.skin)