So constant combinators appear to have the following UI behavior: when changing the value output on a particular signal, both the signal output value and the UI control that lets you set the constant value agree. They are always in sync. Very simple and intuitive.
They can however get out of sync. The idea is that if you declare a signal in a slot, then delete the signal, then reuse the slot, the UI control will have the constant value of the deleted signal, not the new signal. In the image we have the following:
- I place a constant combinator.
- In first slot I create a signal "0". It has value 1, and control shows 1. I change it to 10, both value and control show 10. Good so far.
- In second slot I create a signal "1". It has value 1, and control shows 1. I change it to 5, both value and control show 5. Good so far.
- I destroy signal "0" of first slot by right clicking on first slot. Control still shows 5. Good so far, I think, since if no slot is selected it's fine for the value to not be defined, I guess.
- In first slot I create a signal "2". It has value 1, but control shows 10. UI bug is here. The control has been updated not to the actual value 1, but of the past deleted value 10.
- For good measure in third slot I create a signal "3", both value and control agree it is 1. That is good.
