Neural’s reply to this was
“Because you are not really tapping “undo” with the first tap. Tapping anywhere above the parameter editor will show the grid. A second tap on any control is needed to trigger an action”
Which gave me a lightbulb moment - all these years, I’ve been pressing the Undo button when an Edit window was open thinking that the button would undo any parameter changes I had made (which is what happens in the Headrush and Line 6 universes I think?)
I now realise however that I had fallen foul if somethng extremely confusing ij the user interface; when you edit a block on Row 1, the Undo button is indeed visible, leading me to think it was there to undo parameter changes;
o
I now understand that this is only there by coincidence, and actually it isn’t there to be used in the Edit window at all; in fact it’s on the Grid, even though you can still see it, and tapping ANYWHERE outside the Edit window returns you to the Grid. In my case I happened to be tapping on the Undo arrow, thinking it was part of the Edit window functionality.
I also now see that if you have the Edit window open for a Block on Row 3, you don’t see the Undo arrow, as it is too far to the top of the screen;
This is all well and good, and I’m glad I now understand this, but it is yet another example of the UI being at times somewhat un-intuitive, and I still don’t really understand that the point of the Undo button is, if it is only available on the Grid, other than to jump to previously selected Presets, or undo effects chain order changes.
To make things more confusing, Neural also told me this;
"On Quad Cortex, the UNDO/REDO controls are on the grid itself, so accessing them requires closing the currently open parameter editor. On the other hand, Undo/Redo changes while parameter editors are open is possible on the Cortex Control app. Going even further, there are keyboard shortcuts assigned to undo/redo (cmd/ctrl + z & shift+cmd/ctrl+Z)."
This is of course correct, in Cortex Control, it does work the way I had thought all along it worked on the QC itself - which is great, but begs the question why would CC be different from the QC, and why, why, would you use the same icon for something that actually behaves differently??
Anyway, the net result is that I think it still needs addressing on the QC, and I have set up a feature request to bring the way the Undo works on the QC in line with the (correct way, imho!) it works in Cortex Control
I know some of you are also confused by this, so hopefully this helps clarify things for you too!