I have a patch that:
1. disarms the current track
2. moves to the next track
3. arms the new track
These actions are arranged right to left off a Live.button in the proper order.
When clicking the button with the mouse, the actions happen in the expected order.
When I route a midinote in this way:
route 27 (note pitch)
route 100 (note vel)
...and use my midi controller to send a note, this happens:
disarming: bang < -- print which happens before subpatch is called
arming: bang < -- print which happens before subpatch is called
arm: path live_set visible_tracks 4
next track: < -- print which happens before subpatch is called
disarm: path live_set visible_tracks 5
So it's like the whole top level .amxd patch is executed and then the .maxpats are executed afterward...in left to right order.
Like I said though, this only happens when I use a midi note, which I strip all data off with route and am sending a band to the button (which i saw with the monitor). When control clicking the button, it works fine.
The button with the problem is huge and red.