Gonna have to bear w/ me on this one...
To start, here's an ONSKINSTART that's in my MMIv2.0 skin:
I'm not not gonna bore you w/ the code for each command as they are quite lengthy. The summary of each command is a series of SAVETOSKIN, WRITETOFILE, ADDTOFILE commands to various *.skin and *.txt files that is used in my skin using the INC command line with tons of variables defined in skin.ini
So here is the oddity that I am experiencing.
Let's say you initally start RR with MMIv2.0 as the starting skin. It'll follow the ONSKINSTART command as it should writing to each file w/ details to complete various skin files when loaded.
If you use skin browser to switch skins, say BMV2, even though ONSKINSTART is defined only in the MMI skin's ExecTBL.ini, it'll run MMIv2.0's ONSKINSTART command and write the files in the BMV2 skin folder.
I don't now if that was intended or not, but should this be happening? I mean, shouldn't those ExecTBL commands stay only w/in the skin? I'd hate to think that I'm cluttering up another skin folder w/ my startup files.