Am I doing something stupid? (maybe dont answer that directly). Why would I not be able to move beats around in the blocks? Is there a way of locking them that I missed?
will do when it starts acting up again - can't seem to reproduce at will - reverted back to normal behaviour now and I don't know why - also - not sure if this is a mac thing - but the double arrows seem to get 'locked' and cant revert back to normal 'move' arrow. Behaviour changes though as if the icon has been selected - just the cursor has locked. Remedy is to switch to another active window on mac(like this one!) and then back to Causality.
Are you by chance in the middle of a block move? Is there a flashing button in the upper right?
When you move a block, we put you into a mode where you have to commit or cancel the block move. This is because dropping a block into a new place will thread the beats into whatever else is there in the whiteboard, based on the visual order. If you're doing this accidentally or at a late stage in a script, it's ultra-destructive. And without a commit operation, we'd be doing this for every drag, and moving a block could actually consist of 4-5 drags to find the exact place, where we'd trash your sequence a little bit on every drag if there are concurrent beats in other lanes or blocks. So we make you commit it.
will do when it starts acting up again - can't seem to reproduce at will - reverted back to normal behaviour now and I don't know why - also - not sure if this is a mac thing - but the double arrows seem to get 'locked' and cant revert back to normal 'move' arrow. Behaviour changes though as if the icon has been selected - just the cursor has locked. Remedy is to switch to another active window on mac(like this one!) and then back to Causality.
Ah - it was when whiteboard was full screen -Apologies
Are you by chance in the middle of a block move? Is there a flashing button in the upper right?
When you move a block, we put you into a mode where you have to commit or cancel the block move. This is because dropping a block into a new place will thread the beats into whatever else is there in the whiteboard, based on the visual order. If you're doing this accidentally or at a late stage in a script, it's ultra-destructive. And without a commit operation, we'd be doing this for every drag, and moving a block could actually consist of 4-5 drags to find the exact place, where we'd trash your sequence a little bit on every drag if there are concurrent beats in other lanes or blocks. So we make you commit it.