by Julia Foest » Wed Jul 27, 2011 8:29 am
Hi,
two ideas from my side:
1. Use the scripts for hiding / showing controls.
Example:
Once the CS Button is clicked (to start the fade), it will become invisible until the fade is done.
This can be done in different ways.
First way:
Scripts inside the button (let's say it is the CS Button ID 1)
WDFaderUp,ID,Seconds --> starting your fade
WDControlHide,CustomScript1
WDWait,Seconds --> Waiting the same amount of time you set up for the fade
WDControlShow,CustomScript1
Second way:
When pushing the CS Button the fade should start and the button should disappear.
The fader itself will cause the button beeing visible again.
Scripts inside the button:
WDFaderUp,ID,Seconds --> starting your fade
WDControlHide,CustomScript1
Then you will need a fader input node, linked to two script output nodes.
In the script output nodes you the following settings:
Script node 1: If FaderValue = "max.Value your fader will be" then WDControlShow,CustomScript1
Script node 2: If FaderValue = "min.Value your fader will be" then WDControlShow,CustomScript1
Both nodes set up to update on input change only.
2. Use the script for aborting the current fades .
This way you stop the current fade to start the next one - without having the fader jumping around.
Scripts inside the CS Button:
WDFaderAbortFade,'ID' or WDFaderAbortAllFades
WDFaderUp,ID,Seconds
Greetings,
Julia