That’s really great, to have it a bit more deterministic.
However I think I’m going to find myself very often replicating the old behaviour of “other states” having the new object disabled, by explicitly disabling it on all states then enabling it for the current state.
For example those situations where one song state of 20 needs an extra route, because it needs more keyboards splits than the other song states. With the new version, by default the other 19 states would be left with a dangling target, which would show up as a zone on the on-screen keyboard for all the other states.
So I wonder whether it might make more sense for new routes to follow the old behaviour of being disabled on all other states (but explicitly writing that into the states, for consistency). New objects like racks and plugins probably don’t make much difference either way.
Either way, great robustness enhancement!
Neil