Alexan? thanks for your advice? we will improve it.
Thank you for your reply.
Regarding the forced normal memory mode for single trigger, I'm not sure if this was done intentionally or if it is a bug.
Since there is a model with a low memory (CNL) and a model with the high memory (CML) , I don't understand what is supposed to be the benefit of the 2Mpts memory when the user can not utilize it when capturing a signal. It can only be used while viewing a signal in real-time or randomly stopped (STOP button) and in both cases the long memory makes little sense.
Here is what I describe with images. All images show the 1KHz test signal @250us
Here is an image when the oscilloscope is running in real time (red square) and the memory is set to long mode (green square), Notice the Waveform Preview Display (blue square) that shown the captured length vs what is visible.

Here is an image when the oscilloscope is stopped using the RUN/STOP button (red square), notice that the memory mode (green square) still shows long and the Waveform Preview Display (blue square) still shown the same length as in real time.

Now this is the same signal captured with the single button (red square). Notice that the memory mode (green square) has become grayed and has forced the normal (low memory) mode and the Waveform Preview Display (blue square) is now showing that the captured wave is much smaller that what it was with the long memory mode.
