I've recorded a quick and dirty video (sorry for the quality).
The test signal is a signal pulse with a period of 5s.
Current behavior
Case 1 - Waveform not moving until next trigger in RUN mode:
0s to 8s in the video.
Trigger in NORMAL, running.
A signal is present in the screen, moving with the arrows moves the trigger point but not the signal.
This is no big deal, and maybe other devices do it like this too.
Case 2 - Normal mode goes to WAIT when pressing STOP button
8s to 13s in the video.
Stop button is pressed.
Trigger changes from NORMAL to WAIT.
Moving with the arrows, moves the trigger point and some part of the signal, but the pulse remains in the same place.
When another pulse arrives, waveform is updated with new samples, trigger changes to STOP and the waveform can be finally moved correctly.
The desired behavior:
Case 1:
In my opinion, the arrows should move both the trigger point and the waveform (Like in STOP mode).
But this one is not a big problem, I can live without it.
Case 2:
When Stop button is pressed.
Trigger must change to STOP and KEEP the signal already acquired.
So the last signal recorded before the stop can be inspected with the cursors or zoom.
Why fixing case 2 could this be useful?:
Leaving the scope in RUN mode (NORMAL trigger), until I see an interesting event, pressing the STOP allows me to inspect the event, but ONLY if behaves as requested.
Sorry once more for the video quality, but I think it's good enough to show the problem.