request: exclude command on .skin

**liquid_smoke** · 11-02-2006, 10:35 AM

include/exclude

Currently if you have a command like this.

"IDLE","ESC",configoptions.skin

it will execute the IDLE command only when on the configoptions.skin

is it possible to have something like this

"IDLE","ESC",<configoptions.skin

im using < as exclude and > as include these can be changed to whatever character thats still available for syntax

exclude would allow the command to be sent to any .skin except the one listed
include would allow the command to be sent only when in the .skin listed (current functionality )

This way say i have a command that gets sent to RR based on specific conditions from and external app or even from inside RR, but there are certain screens i never want this command to be activated on and RR to simply ignore it.

Also, im not sure if its possible to list multiple .skin files in the examples above, but if not somehow enabling that would be great too so you could have something like this.

"MYCOMMAND","COMMAND",<configoptions.skin,audiopla yer.skin,radioplayer.skin,

Which would allow the "MYCOMMAND" to be executed on all screens except the ones listed.

For skins that have a ton of .skin files the current method would mean i would have to setup the same command and .skin list for almost every .skin except the ones i wanted like this.

"IDLE","ESC",configoptions.skin
"IDLE","ESC",menu.skin
"IDLE","ESC",audioplayer.skin

My skin for example has 144+ .skin files so this list would be really,really long and would also have to be added to when any new .skin files were created.

Since its already possible to list a .skin file for a command to only be executed on, we really only need the opposite of that so instead of < and > just <my.skin is needed.

is this doable?

**Enforcer** · 11-02-2006, 10:42 AM

Hmm, interesting.

I can see people getting in trouble with that though. (forgetting to exclude it out of new .skin files for example, that really need excluding from it.)

Although I bet chuck has already got a workaround for this.

**liquid_smoke** · 11-02-2006, 10:52 AM

well if you set it up right, you shouldn't have to manage it at all.
usually the exclude list would only be used on a small number of screens that have a specific reason why you never want it active on those screens so that list likely wont grow.
If you have a long exclude list its better to use the include option like we do now.

**guino** · 11-02-2006, 01:39 PM

you can do this with a global command and making the exceptions as desired:

Your EXCLUDE list would be:

"IDLE","",configoptions.skin
"IDLE","",menu.skin
"IDLE","",audioplayer.skin
"IDLE","ESC"

As opposed to a INCLUDE list (normal style), that could be:

"IDLE","ESC",configoptions.skin
"IDLE","ESC",menu.skin
"IDLE","ESC",audioplayer.skin
"IDLE","" (This is actually the same as nothing)

As you can see, you can specify a GLOCAL command for all non-listed screens, that is, so you just list the exceptions (just as you would your way).

**liquid_smoke** · 11-03-2006, 11:27 AM

ah, some times the solution is soooo simple you dont see it.

thanks

**kolemieux** · 11-03-2006, 07:41 PM

When Guino answers some of this stuff my freakin head spins.... It's like he has written the damn dictionary and knows every word - and if a word does not exist he creates one ....

The power of RR is simply incredible...