Normaly the binding should first deactivated… but it fires the controller at first and then deactivates
on a second click the binding is working…
Thanks for reporting - I’ll look into it.
Brad
I’ve made a fix for this for the next build, but there’e once caveat that you should be aware of.
In the next build… the disabled binding won’t fire on state change any more. However when switching to the state where the binding is enabled, the binding will fire twice with the same value.
The reason for this is as follows:
-
Bindings that reflect a source value (as opposed to bindings triggered by an event) fire whenever the binding is activated (ie: enabled) to ensure the receiver always has the correct value. ie: when switching to a state where the binding switches from disabled to enabled, it will always fire.
-
Because the selected state program number also changes during the state switch, you get a second event triggering the binding.
This could be quite tricky to fix and I’m not sure if it’s important or not, so I’m leaving it for now.
Brad
Problem with disabled binding firing should be fixed in 3571 available now.
1 Like