execTBL

**millsy** · 05-06-2009, 11:56 AM

Im trying to get a handle on how the execTBL works and Im hoping one of the skinning gurus can help me. For a start when is it read,is it when RR starts or is it referred to when required,if so how does RR know when to look in there,is it when it encounters a command it scans the ini,exec or somewhere else.Is there a reason why commands are here and not in skin ini? Without knowing how and why this works it is impossible to faultfind or modify,or just to know how a particular skin works.
For example i was just reading the documentation for the Spidermunz silabs plug in, in it he mentions to insert the following command "CLOSEWINDOW:SDKSilabs l l QUIT" into the 'quit' of roadrunner.In this example i assume it goes in the execTBL.ini,why there and not in the radio skin file? ONSKINSTART is another popular one is it read by RR when RR starts or when you leave a particular screen in the skin?
I realize it is a bit much to try and explain in a couple of lines but any help with this will be much appreciated.

**Sal R.** · 05-06-2009, 12:07 PM

Exectbl is read and processed when rr starts. All commands are defined on startup.

skin.ini holds skin specific variables that are needed on skin startup. The values can be changed using commands like "SETVAR, SETVARBYCODE," etc. See Skin Commands for more details. Depending on how good a skinner you are, you can use skin.ini to hold simple commands (AUDIO, VIDEO, etc.), but more complex commands will have to be defined in ExecTbl.ini.

For example i was just reading the documentation for the Spidermunz silabs plug in, in it he mentions to insert the following command "CLOSEWINDOW:SDKSilabs l l QUIT" into the 'quit' of roadrunner.In this example i assume it goes in the execTBL.ini,why there and not in the radio skin file?

You can it either way. In the skin file or in ExecTbl. All a matter of preference.

ONSKINSTART works just how it sounds. When the skin is first loaded (i.e. when RR starts w/ a skin that uses "ONSKINSTART" defined or switch to it using skin browser.)

**Sonicxtacy02** · 05-06-2009, 01:13 PM

thread moved to Road Runner SubForum

**millsy** · 05-06-2009, 04:39 PM

Thanks for that,if i can bother you again with another example,i will take it from the carwings skin it is a big one!

"CWDSETUP","SetApps||SetCommandLabels01||SetAppLab els||SetIcons||$default$"
"CAMERA","LOAD;RRCam.skin||run;$skinpath$RRCam\RRC am.exe;RRCam.exe"
"COVERFLOW","LOAD;COVERFLOW.SKIN"
"GMPC_OVERLAY","RUN;$SKINPATH$ElcosMenu.exe|GMPCOL .skin"

If this small part of the execTBL is being executed on startup that would mean for example the camera skin,coverflow,Gmpc overlay are all being started,would they then be running in the background?

**guino** · 05-06-2009, 05:04 PM

commands on exectbl are not really "executed" until the command on the left comes up, which will then cause RR to execute the command on the right of the same line instead. It's a translation table so to speak.. there's more info on the top of exectbl.ini

**sxtnitehawk** · 05-06-2009, 10:43 PM

yeah, the only commands that are executed at startup are those defined in "ONSKINSTART" and "ONRESUME" as far as I can remember without looking at my exectbl...

one thing you'll learn, is you can have nested commands, basically having a chain of commands called one after the other.......just dont try to put multiple commands in a byvar.......that dont work, lol

it all looks confusing, and at first glance, seems rather limited to it's abilities, but once you get into it and know more about what does what, you'll see that RR is extremely powerful because of it's flexability........and it just keeps getting better thanks to experienced skinners, programmers writing plugins, and hardware makers that give us more and more options all the time

(people like guino, BlueZX3, Enforcer, Toaster, greenman, SonicExtacy, and all of the others whos usernames i cant remember off the top of my head)

the more people that use it and learn how to really USE it, the more advances the program will make. I try to give ideas when possible, and I'de like to think that I have at least, in part or some way, helped to better the community

**millsy** · 05-07-2009, 02:18 AM

Originally Posted by guino

commands on exectbl are not really "executed" until the command on the left comes up, which will then cause RR to execute the command on the right of the same line instead. It's a translation table so to speak.. there's more info on the top of exectbl.ini

So this must work in a similar way to the old B.A.S.I.C. interpreter of days gone by, when a keyword is read (in this case a RR command)it scans a lookup table for the appropriate action to be performed,again in the carwings example "GMPC_OVERLAY","RUN;$SKINPATH$ElcosMenu.exe|GM PCOL .skin", where GMPC_OVERLAY is not a Valid RR command it must be defined somewhere else,where would that be? If the analogy i used above is correct then i am well on the way to at least understanding how it works.
Even though i dont understand all of it i do appreciate the skill and work that has gone into creating this program and some of the great skins.

**sxtnitehawk** · 05-07-2009, 02:23 AM

GMPC_OVERLAY is the command definition in execTBL...

for instance, here's some of mine:

Code:

"CHECKRADIO","BYVAR;NOFM;SOURCEFM2<<CHECKXM"
"CHECKXM","BYVAR;NOXM;SOURCEXM2<<CHECKSR"
"CHECKSR","BYVAR;NOSR;SOURCESIRIUS2<<MSGNORADIO"

"CHECKRADIO1","BYVAR;NOXM;SOURCEXM<<CHECKSIRIUS1"
"CHECKSIRIUS1","BYVAR;NOSR;SOURCESIRIUS"

"CHECKRADIO2","BYVAR;NOSR;SOURCESIRIUS<<CHECKFM2"
"CHECKFM2","BYVAR;NOFM;SOURCEFM"

"CHECKRADIO3","BYVAR;NOFM;SOURCEFM<<CHECKXM3"
"CHECKXM3","BYVAR;NOXM;SOURCEXM"

"RADIOPRESET","GETPREFIX||GETPVALUE||SAVETOSKIN;$RPREFIX$PRESET$PRESETNUM$;$PVALUE$"

"GETPREFIX","BYVAR;ACTIVESOURCEID;<< <<SETVAR;RPREFIX;FM<<SETVAR;RPREFIX;XM<<SETVAR;RPREFIX;SR"
"GETPVALUE","BYVAR;ACTIVESOURCEID;<< <<SETVARBYCODE;PVALUE;FREQUENCE<<SETVARBYCODE;PVALUE;TRACKNUMBER<<SETVARBYCODE;PVALUE;TRACKNUMBER"

"SOURCESIRIUS","SETSOURCE;SIRIUS||SETIND;!CUSTOMsrind;ON||SETIND;!CUSTOMfmind;OFF||SETIND;!CUSTOMxmind;OFF"
"SOURCEXM","SETSOURCE;XM||SETIND;!CUSTOMxmind;ON||SETIND;!CUSTOMfmind;OFF||SETIND;!CUSTOMsrind;OFF"
"SOURCEFM","SETSOURCE;RADIO||SETIND;!CUSTOMfmind;ON||SETIND;!CUSTOMxmind;OFF||SETIND;!CUSTOMsrind;OFF"
"SOURCESIRIUS2","LOAD;radio.skin||SETSOURCE;SIRIUS||SETIND;!CUSTOMsrind;ON||SETIND;!CUSTOMfmind;OFF||SETIND;!CUSTOMxmind;OFF"
"SOURCEXM2","LOAD;radio.skin||SETSOURCE;XM||SETIND;!CUSTOMxmind;ON||SETIND;!CUSTOMfmind;OFF||SETIND;!CUSTOMsrind;OFF"
"SOURCEFM2","LOAD;radio.skin||SETSOURCE;RADIO||SETIND;!CUSTOMfmind;ON||SETIND;!CUSTOMxmind;OFF||SETIND;!CUSTOMsrind;OFF"

the defined command name is on the left, with what that command performs on the right...

does that help explain better?

execTBL.ini is where you create all of your custom commands as well as manipulate internal commands...

**Sal R.** · 05-07-2009, 10:18 AM

Originally Posted by millsy

"GMPC_OVERLAY","RUN;$SKINPATH$ElcosMenu.exe|GM PCOL .skin", where GMPC_OVERLAY is not a Valid RR command it must be defined somewhere else,where would that be?

GMPC_OVERLAY is the command you'd use in a button code in a skin file.

i.e.
B00,...,"GMPC_OVERLAY",""

When the button is pressed, RR will process the command GMPC_OVERLAY and execute the command line in ExecTBL.

For clarity, RR will execute "RUN;$SKINPATH$ElcosMenu.exe|GMPCOL.skin"

**millsy** · 05-07-2009, 04:52 PM

Im getting this !
So the command doesnt necessary have to be defined anywhere it can be, for example a button definition or a plug in command or a RR command etc.hence what is in the exectbl file
"This (OPTIONAL) file contains translation commands.
/, RR will accept the commands defined on the LEFT
/, and execute them as expressed on the RIGHT"
as all have pointed out and does now make a lot more sense,shall now have to study the (very large and overwhelming)list of RR commands and meanings
Thanks all this little discussion has been enjoyable and enlightning.
Now i guess im going to have to study sxtnitehawk's file and