This MO is normal when complex use of the trigger suite is required. Hit STOP than do the measurements, zoom in or out on a captured waveform. Why be challenged by the proper use of a scope ? ![Wink ;)](https://www.eevblog.com/forum/Smileys/default/xwink.gif.pagespeed.ic.cldandycH0.png)
Normal (from my experience of having seen many many many different people use scopes) is that users do not expect to collect any data outside the visible window. Trigger on what you want and then inspect as needed.
Its this ridiculous leap to a small number of people now saying capturing outside the window is a must have feature, so they can see a slowly triggering characteristic, then stop (before another trigger), and see some other correlated data.
A zoom window is pretty much the obvious solution to that, see both, and have fast/direct control of memory size and position.
There is NO scope (that I'm aware of) that lets you set the trigger position within the overall capture
and the screen location independently, trigger position is relative to screen (and all that outside the screen is invisible). Which is why the zoom window is so important to explain/discuss, it adds those controls so the user can set every parameter (reducing the size of the view, but now including a view of the entire capture).
But I'm sure nctnico will continue shouting over any reasonable discussion of the
pros and cons of different methods:
Zoom out; pros: bigger picture of part of the signal, cons: limited control of positioning
Zoom window; pros: see everything and control all positions, cons: smaller waveform size
The user can choose what is most appropriate to them, from my perspective it is very hard to imagine common or routine use cases for zoom out, the benefits just aren't there.