GitLab

unequal values the next change re-sets the values equal to each other
again.  Putting in new blocks is used as the new value to lock to.
It doesn't work perfectly with undo, but this is the best I can do with
the way the Blockly event system is architected.  The worst behavior is
when you change radius 1 and 2 in an alternating pattern - you lose half
the states to the locking system overwriting what was supposed to be the
new value.  Otherwise, changes to 1 or 2 will work fine except you get an
extra undo state in there - you have to click twice to go back.