Printable View
I use ONSKINSTART to activate the VISU everytime I open the audio player.
With the VISU I have many problem so I prefer to close it when I go out from audio player where. If I close RR with the VISU on, Winamp remain open, after when I reopen RR it couldn't start properly because it tries to open another section of Winamp.
Quote:
Originally Posted by Blue ZX3
Seeing as he misunderstood what ONSKINSTART does, chances are ONSKINEND is not going to be the command he's after ;)
It's simple:
I use ONSKINSTART,VISU,audio_player.skin to activate the VISU when the audio player skin is opened and I close the VISU when I exit from audio player.
why not just use AUDIO||VISU as your audio player command. No ONSKINSTART needed.Quote:
Originally Posted by JohnnySierra
Quote:
Originally Posted by Enforcer
And this just proves it.Quote:
Originally Posted by JohnnySierra
@Johny
The "ONSKINSTART" is just like the windows startup folder, it only runs when you start up the computer, and onskinstart only runs when you first load a skin. The word skin refers to the whole collection of screens in a skin, each screen is a skin file but not called a skin but a screen and think that is what your misunderstood.
Thanks for the clarifications, but I have another question.
When I use "ONSKINSTART,command,xx.skin" the specified command is executed referring to the xx screen. But at the startup the xx screen isn't visualized, so when has the command effect?
And about the screen when I load, for example, the browser screen from the audio player, remains this (audio player) loaded in the background or not?
banghead
No, the "ONSKINSTART" is mostly used by most to help setup the skin(set labels,set commands for dyno buttons). If what your trying to do is simply have it go to another screen after its done loading then you can either...
#1 add "startcommand=Load;xxx.skin" to the rr.ini file
#2 add "||Load;xxx.skin" to the end of the ONSKINSTART cmd in whichever skin your trying to modify
I think you still have some terminology to learn with RideRunner
Example:
In ExecTBL.ini:
"ONSKINSTART","AUDIO||VISU"
When the skin is loaded (RR startup or skin change), RR will EXECUTE AUDIO||VISU commands.
That's how ONSKINSTART works. It executes commands on skin start.
That is the only time ONSKINSTART is used. On startup.
I don't know if it's still loaded in the background because I've never tried it, but I'm guessing...yes.
Ok,
so the correct use is "ONSKINSTART","command" without xx.skin.
And what about my second question?
Quote:
When I load, for example, the browser screen from the audio player, remains this (audio player) loaded in the background or not?
Yes, RR will keep x screens in memory, where x is the screen limit set forth in the rr.ini and/or config. The setting is screenlimit=x. When you load a screen that isn't already loaded and in doing so would put the screens loaded count past the limit set, RR will first unload the oldest screen thats in memory and then load which ever one you were going to.