I have a suggestion regarding the behaviour of the stop back key. If there are cues with links or loops the stop back key doesn't respect those, and I think it should. For example, if we have cues 1,2,3 and for some reason we put a link from 1 to 3 so that 2 is skipped, hitting back on cue 3 goes to cue 2, whereas I suggest that going back to cue 1 is more useful. Similarly, if a loop has been exited and back is pressed, the last cue is reentered with the lop count at its starting value, I'd suggest it ought to be at 0, so that when go is pressed again the whole loop doesn't execute all over again.
If I've missed something, and it is possible to set up the desk to behave as I suggest then my apologies, and I'd be happy to be pointed to the relevant documentation to help me understand better.
I appreciate that this will entail keeping extra back pointers in the cue list and changing the list node structures so I'd understand if this is a low priority.