At the moment, the valueChangeTrigger is hardcoded to always fire its trigger whenever its source input is changed, regardless of whether the underlying value has actually changed. This can be useful in cases where you want to be able to set the same value repeatedly and have the trigger re-fire each time. However, users may want the trigger to only fire when the actual signal value of source has changed and not when it was swapped for another unit generator that is currently outputting the same value.
At the moment, the
valueChangeTrigger
is hardcoded to always fire its trigger whenever itssource
input is changed, regardless of whether the underlying value has actually changed. This can be useful in cases where you want to be able to set the same value repeatedly and have the trigger re-fire each time. However, users may want the trigger to only fire when the actual signal value ofsource
has changed and not when it was swapped for another unit generator that is currently outputting the same value.