[?] Inhibit customscript button pressure

[alverman]

It 'can prevent or inhibit the push of a button customscript?
It happens that when I perform a crossfade of two layers if you press the button again before it is finished the crossfade faders start to dance.

Then how do I take simultaneously the value of a fader at the time of WDFaderUp,'ID', 'Second' ? (SOLVED)

Many thanks, Alberto

[Julia Foest]

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

[alverman]

Thanks Julia had not thought of:)
What do you say, do you think it is appropriate to include in the request for an option of whislist Button status (enable/disable) with control WDButton, 'ID', 'Status'?

Alberto

[Julia Foest]

Hi,

There is already a mute click option in the buttons as well, here you can set up that the button click will not be executed for up to 2 seconds after the first click. But it is not adjustable for more then 2 seconds.
I'll forward your wish for having a mute button script.

Greetings,
Julia

[alverman]

Let's see what else to ask today

More thanks Julia

[alverman]

Your advice works great, the problem is that if during the fade change the page Button also appears on that page.
I think the implementation of the state of the button is the only solution.

Alberto

[Julia Foest]

Hi Alberto,
sorry I don't understand what the problem is. Can you explain it again?
Thanks,
Julia

[alverman]

Ok Julia
If I run the crossfade, which hides the Button that runs it and I move to another page on a crossfade at the end of the Button appears on the page where I am.

[Julia Foest]

Hi Alberto,

ok, I understand.
Two things:
1. Why do you need a Button Hide if you go to another page in the same moment you push the button?
2. If you want to hide the button on the page (let's say the button's page is called BUTTON), use the command WDControlHide,CustomScript1 as well as your WDPageGoto-Script inside the button. And if you go back to the BUTTON page, you can make it visible again by the page's start up macro script. To set up the script do a rightclick on the BUTTON page GUI, choose Item Properties. Here in the textfield on the bottom type in WDControlShow,CustomScript1.

Greetings,
Julia

[alverman]

I start crossfade with button READY TO GO from crossfade page (photo 1)
While the crossfade is still running (photo 2) I go to cue page (photo 4)
When crodfade finish the CSButton appear in cue page (photo 3)
I return on Cross fade page (photo 3)
I go to cue page and CSButton is no longer visible (rightly)