I could have this working except for one of these two commands are required; RELOADALLSCREENS or UNLOADALLSCREENS
RELOADALLSCREENS disables gestures
UNLOADALLSCREENS disables transitions
I am lost now. No matter what when switching directions it does not want to work. Maybe a new feature like this can be implemented into a future RR release or maybe someone else can figure this out and make a plugin or share their codes.
Hopefully Guino and Mitch will help you solve this issue one way or the other! I have buttons to change/navigate pages, I could design a much better skin without those mostrosities, make all skins look like an ATM machine, IMHO. The way iOS, Android, and now Windows 8 do it is so much better.
"EFFECT" - This allows you to dynamically select the effect used when trasitioning FROM the current screen to another.
Example: "EFFECT;0" (fade) -- check /EFFECT skin parameter above for range of values.
I'm not sure I understand what that issue is. To be honest, the feature with effectin/out never made much sense to me (you're always going INto a screen and OUT of another at the same time), the distinction made is if you are going to a screen that you've browsed before the one you're currently in, then you're going "out" of it - note that this is unrelated to the screen being loaded as the previous screen could have been discarded. So I am not 100% sure of how the logic was supposed to be for these, however, you can try setting transition=-1 on skin.ini or rr.ini and then use the effect command to set the transition from one screen to another (should not matter if the screen is loaded or not) - you can also use /EFFECT in the skins to define it to whatever, but for dynamic changes it would get messy. The only thing the screen being loaded or not will change is that when you load a screen it sets the effect based on the ini settings (transition[in/out]) and resets everything on the screen, as opposed to keeping it loaded preserves the last state.
What I have found is there is maybe a memory order to it. Say you are starting on screen 1 and then go to screen 2. It will always do the IN EFFECT for screen 2. If you are on screen 2 and then LOAD screen 1 it will do the out effect of screen 2. This is fine if you are only using gestures, but once you start adding in buttons as well it gets confusing. I think this is more useful for applications, where you just load the application and it will do the IN effect, then when you use the BACK command it will do the OUT effect.
I think I have figured this out using the EFFECT;X command however it seems to only work with screens which have already been loaded, preloaded screens do not count. I'm not sure why this is.
I think if I set up an on skin start command where it goes through a sequence of loading each screen perhaps off the visible screen, then the transitions will work the way they should. I'll post more after I test this.
id also think a .skin with a /EFFECTxxx = command would override
so if your doing some funky stuff, i wouldnt have any /effectxxx commands in them, unless its a popup
i think i know what you want to do, swipes to go back and forth, like viewing images on iphone
you might be outside the box on what we have in RR
so good luck
i like transitions for a while, then i dont use em for long :)