In my opinion he is not "almost hysterical to make problem where there isn't one" nor "drama" being made. It may be no problem for you and many others, but it can be annoying for some. I don't know where you found that problem bother "very little people", "very few...", maybe your affirmation is because it doesn't bothers you, or that you have not seen it mentioned before. And something annoying in your daily work tool is disgusting. To me yes, it is a problem. And as pointed above, other models allow turn it off.
I agree that Daniel is a nice gentleman, but we can disagree with him. We are in a forum with many different user experiences, opinions, preferences, and so on. No one here are disrespectful with him, that yes would be unacceptable. I, for one, do not buy his answer saying that it is a feature (intentional) when in another Keysight series it is allowed to disable it.
Another point is that if the OP is a new member or not, it has no significance at all, in fact the OP is a older member here (since March 2013).
As pointed before in other threads, it seems that some brands can not be questioned. Bugs becomes features...
Hehe, you're barking up the wrong tree..
I don't play preferences.. It's mine hard earned money I buy this stuff with. I take no crap from anybody, ESPECIALLY Keysight or other A brands, because i expect perfection from them, for the kind of money they charge.
And believe it or not, in mass produced product, many outnumbers few. Development costs real money, and is put towards real capability, not some details only few think are problems. If Keysight got several thousands complaints about this it would be changed many years ago.
Other models are actually based on completely different code base (3000T/4000/6000 share platform) and it is there by code modularization because of touch screen interface. 3000T still automatically enables cursors when you add measurements, and by default cursors are there so standard behaviour is the same.
And I disagree with Daniel. I participated in topics about options updates and bugs in Keysight scopes. I'm sure Keysight wasn't glad about what I proposed there and what I think what they should do. But make sure that you know the difference between Daniel, the person, and Keysight, company he works for..
And about this particular thing, yes I don't think it's a problem.
By OP own statement "I have the scope for 9 year now and I realized just recently how annoying it is."
... really... It is really hard to take that statement seriously, really....
And op has 40 something posts.. Makes him a person that is not active here, new or not. I don't make background checks on members, so between low post count and posts that are a bit off in etiquette here, I presumed he was new. I was wrong, thank you for setting me straight. I'm not sure how is that relevant though and that it makes any difference to the topic.
You cannot decide that some manufacturer's design decision is bug because you say so.
I would like that my scope had more memory. Surely it is a bug, I demand they fix it.. It doesn't work that way.