I work with two video flux and I implent in my Visio view a button to switch between those flux.
The process is to disabled the first one before to activate the second one.
During this process, I want to display a new shape from a script which will be triggered by the change of a value, in my case when the status of my first flux will change to "Disabled".
I try the following shape data in the previous shape display but I'm not sure of the syntax :
Execute :
Script:Script_Pause_After_5s||ShowPause=PauseDisplay|||NoConfirmation|Trigger=[Event:Disabled,14010:{8DC4C9E5-03CE-4801-86B7-2ACEDD4F04AF}]
Hi,
I could not find any reference of the “Disabled” event existing, only IOClicked and NodeDoubleClicked seem to be options.
Now if I understand what you are trying to do, using Trigger=ValueChanged should also work. This will retrigger the automationscript when one of its inputs has changed, so you would only need to add the parameter of that first flux that contains that “Disabled” into the automationscript.
I do not know your exact setup but for reference, this shape data will retrigger the script every time the param 1 on element 1 changes:
Execute: => Script:Information||Input=This runs when value changes;trigger=[param:956/1,1,]|||NoConfirmation|Trigger=ValueChanged
The automation script does not need to specify this “trigger” as an input but you could use it as input and then check in the automationscript if it was set to Disabled.
Please let me know if this fixes your issues
Hi,
I could not find any reference of the “Disabled” event existing, only IOClicked and NodeDoubleClicked seem to be options.
Now if I understand what you are trying to do, using Trigger=ValueChanged should also work. This will retrigger the automationscript when one of its inputs has changed, so you would only need to add the parameter of that first flux that contains that “Disabled” into the automationscript.
I do not know your exact setup but for reference, this shape data will retrigger the script every time the param 1 on element 1 changes:
Execute: => Script:Information||Input=This runs when value changes;trigger=[param:956/1,1,]|||NoConfirmation|Trigger=ValueChanged
The automation script does not need to specify this “trigger” as an input but you could use it as input and then check in the automationscript if it was set to Disabled.
Please let me know if this fixes your issues