The preferred way to deal with that is to set up the decoding until it works fine
Rookie's method (trial and error) to set up the decoding?
I prefer to use an informed choice for the thresholds.
PS.: I think rf-loop has an important point.
What does the manual say? The latest manual (EN01D) gives the same example as older versions to set the image format, default path and basis filename for screenshots together with some options for the visual appearance in chapter 29.3.2 on page 317. This is still valid even for the unreleased V1.6.0 beta firmware. This example isn’t a particularly good one, because BMP is certainly not the screenshot format of choice; what we really want is PNG!
Shame on me, I was still on EN01C. But as you say, EN01D is no different (well, they chose to replace a font in EN01C that was really nice to read, particularly on screen, by one in EN01D that's rather awful on anything but printed on paper).
On the issue of the default path: Pages 312 to 314 each show a menu that has the option "Save Path" or "Recall Path" with "Internal" and "External". These options do not exist on my scope. When saving/recalling via mouse or on-screen-finger one can choose this via the file manager. This does not work, though, when hitting the PRINT button. So, concrete question: How do I set the scope up such that after powering up, without messing with menus first (i.e. by default), hitting PRINT saves the screenshot in a particular folder, that is not called 'SIGLENT', on the thumb drive?
The page you're mentioning explains all a sort of things by using menus. It does not explain how to set up defaults. In fact, the only sentence in the manual where the word 'default' refers to a path, is "The default save path is \SIGLENT\." (Page 318 EN01D)
I’ve never tried it (I do not use a mouse), but it’s said that the mouse pointer is not visible in the screenshot if you move it to the border of the screen.
I do not use a mouse either, as it takes too much space on a lab table. A trackball is just perfect for this purpose. What I cannot stand at all is fatty fingerprints on screens.
In any case, your suggestion is off the point. During normal workflow I would create screenshots during the development work, and when writing documentation, I choose from those. During development I do not have documentation on my mind, and certainly would not care where the pointer is. I wonder if this would be much different for anybody.
Since I’ve currently not set up a network connection, I do all picture transfers via USB stick at the moment. This includes 4 DSOs, where the SDS2000X Plus and HD see the most use by far and the USB stick is plugged and unplugged dozens of times a day. Never ever did I have any issues like that.
Same for me, I also used to save directly to my NAS, but I'm without network at the moment. So it's possible the issue was there before, I just didn't notice because I did not use thumb drives at the time. Well, I'll keep watching out, might be a hardware issue.
Cheers Peter