Can the confirmation for Auto Setup be turned off (disabled)?
My old HP scope does not do this.
It really does hold me up having to go back and press Continue.
At present, you can execute it by pressing the "Auto Setup" physical button twice.
The Wanted Features list have added whether a second confirmation is required.
Removing confirmations on functions that reconfigure many settings on a scope you just took 10 minutes to setup is bad idea in my opinion.
"This operation will format your drive C:. Do you want to continue?" Definitely good to have confirmation sometimes. Auto and Default button should have confirmation, if you ask me...
If I may give advice to people posting here:
To add some new feature or change some way of doing things on whole platform of scopes takes resources(because if they change how windowing works, for instance, it is now like 10 scopes to be changed, regression tested etc..) .
Sometimes significant changes, which might not be obvious from user perspective.
Feature requests that expect features of 3x higher class of scopes are unrealistic. Let's be real here.
Changes in UI, behavior etc. that are based on personal preferences and/or simply wanting for a device to work in different way just because are also not realistic.
If you want a scope that works exactly like "that other brand" it means you should buy "that other brand". One manufacturer will never exactly copy other one for various reasons.
Every new product will have it's own idiosyncrasies. That is just fact of life.
What needs to be reported are bugs : if you enable Video triggering and it doesn't work, spend some time figuring out what happens so you can report it in a way that will be reproducible.
Any bug that is reproducible, immediately goes into Siglent's pipeline. No kidding. Sometimes takes time to make fix and for fix to reach FW update, but bug report goes into pipeline in a matter of hours.
They fix bugs, because that is what is their responsibility and they wish to have good reputation of well working products.
That is something that is in their interest.
But bug must be a bug to be fixed. A malfunctioning function. Fact that you think something should work differently is not a bug, per se. It might be, but also you might just be a picky eater... Just saying.
As for feature suggestions, let me be blunt: these are not feature
requests. Those are suggestions and wishes.
If you don't have separate paid contract in addition to your bought device, where you a paying for the service of developing custom instrument, manufacturer is not obliged to listen to all the whimsical musing of all of the 7 billion people on the planet.
Go to Keysight or R&S and demand features... We have Paul here from R&S and he can explain how it works. If manufacturer can make some changes they will gladly do it, if possible (technically) and if it is appropriate to the device class and if it fits in their long term strategy.
As for suggestions and wishes, it is wise not to get lost in trivial.
Ask for things that from experience it was proven that this and that would make your life easier. If a function that is 3 levels deep in menu is something that you use all the time and it is waste of time, and if 100 users in the world ask for it, it might be considered.
If one person doesn't like it, and 10000 other users don't care, there is large chance it will not be considered. Just being realistic here.
Also, explaining use case and providing a good rationale behind the feature request is necessary to make a case for the feature.
To put it simply, explain why it is USEFULL to have a feature. Fact that you simply like something or not is not necessarily relevant.
Otherwise we get to story of the boy who cried wolf all the time...