kuo, that would work, but it's not very clean. What you want to do is this.
Define commands in ExecTBL.ini that are skin-specific. The idea is it only gets executed when that skin is active. For example,
"VOL_DOWN", "Vol-", audio_player.skin
"SCROLL_DOWN", "DOWN", audio_browser.skin
Then in Girder, define two separate commands that send "VOL_DOWN" and "SCROLL_DOWN" to Road Runner. Then map your powermate button to BOTH of those commands.
Here's how it works. You rotate the
Power Mate knob. Girder sends BOTH commands to Road Runner. Then depending on which skin is currently active, only one gets carried out (or none at all if you're on another skin).
The posibilities are endless. You can have one button do 20 different actions on 20 different
skins. That's exactly how I programmed my remote control.
One suggestion I mentioned to Guino was the ability to embed the skin-specific portion to a remote command (from Girder). For example, if RR sees "DOWN;audio_browser.skin" it would only do "DOWN" if audio_browser.skin is active. This way, we wouldn't even need to define those skin-specific commands in ExecTBL.ini.
Anyway, this is a very convenient and underrated feature of Road Runner. No other frontend has it. I think we should sticky a tutorial for it.
Bookmarks