Inconsistent executor Size when blocked by another executor.

Not sure this is intended or not, This works with or without a sequence assigned to an executor; If you change the height of an executor and that height change is blocked by some other used executor the operation succeeds in the background but does not happen on the fader since the operation is blocked. If you later delete the blocking executor the executor is resized to fill the required space.

For example:

• Assign Executor 201 and Exit
• Assign Executor 101
• Click on the Handle Tab then click on 200, 300 or 400 (the executor size does not change as expected since it it blocked by 201)
• Delete Executor 201 (Executor grows to the size selected in the previous step).

I guess this isn't necessarily a bad thing since I just deleted the executor in the way but the only feedback is in the Command Line

OK: Page 1.101 "HEIGHT" x

And listing the executor shows the height you selected.

If you attempt to do the same in the UI with the width the columns are greyed out as you might expect. However you can still set the property using the command line and get the same effect:

Set Page 1.201 "WIDTH" 5

OK:Set Page 1.201 "WIDTH" 5

Lastly, if I don't first assign a sequence to the executor, then delete the blocking executor (letting the executor grow), then assign a sequence or store to the executor it snaps from it's grown size to its original size.

Nothing bad, just odd?

Quote from Ryan Kanarek

When you assign an object to the executor (and pressing Store then the exec is actually Store Sequence, Assign Sequence to Exec) you're asserting the properties of the selected Exec Config object, thus snapping to that size and button/fader/knob assignment.

Copy that, not sure why I would ever assign nothing to an executor but good to understand how that works.