The firmware is the latest at V1.1.3.6. The 'on'/'off' lowercase complaint is really just a styling annoyance, making the software look cheap IMO (the older DSO models such as the SDS1104X had good case styling). It makes me laugh a little bit writing this because it is a minor thing, but I think it would be nice if it would be addressed to be 'On'/'Off' (title case).
The second point of the menu popup behaviour being annoying is probably more important. Like I said, when activating the measurement function from the hardware button the measurement menu comes up on the screen. Due to the small size of the display almost 20% of the display is gone. One has to wait 3s for the menu to automatically go away, or manually dismiss it by touching the screen. I would propose that the measurement button should not bring up the measurement menu when clicked, and that the user should have to click the 'MEASUREMENT' button on the touch screen if they want to access the menu. Note that when I say measurement menu I mean the configuration settings for the measurement function, not the actual measurement text that comes up... it is obviously good that the measurement text comes up when you hit the measure button
You asked what other people think? My 2 c..
on/off is consistently same case on every single on/off item I cared to look at. After about a dozen I checked, I gave up.
So it is consistent.
But I agree. It should be ON/OFF.
Which incidentally will reduce boot time to 5 seconds, and BW to 400Mhz.
Not.
Who cares? Is this really only thing you have to report? This is something to be FIXed? Why? What is the defect?
I searched on the Google, and nowadays it is mostly just stupid Apple power icon (with no text) or on/off or ON/OFF as customary. So Siglent is within current state of what is considered mainstream. Nobody is using On/Off...
Side bar is THE menu for everything. This pops up so you can choose here options you need.
Are you letting us know you plan to "redesign" whole user interface?
I mean, fine, if that makes you happy..
But don't expect anybody to go in and rewrite a scope platform because you personally don't like it...
And also use the scope for 6 months before proposing "better" solution.
One data point: the way GUI is made is such so you can use scope without any buttons.
Buttons are only shortcuts into place in a menu.
I would suggest investing your time into learning to use the scope for measurements and if you find an error in functioning report that.
And please don't become eTobey 2.0 (actually 3.0 because in meantime he is now 2.0) and open topic for every single little thing you think you need to say to the word. There are (too) many already opened topics for this.