Bug 389578

Summary:	Marble 2.2.20 (17.08): New right-click rotation feature is prone to misclicks and cannot be disabled
Product:	[Applications] marble	Reporter:	Kevin Kofler <kevin.kofler>
Component:	general	Assignee:	marble-bugs
Status:	RESOLVED FIXED
Severity:	normal	CC:	jjm
Priority:	NOR	Keywords:	accessibility
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Kevin Kofler 2018-01-29 00:49:09 UTC

I use Marble 2.2.20 from KDE Applications 17.08.1.

https://phabricator.kde.org/D5650 introduced a new feature that allows to rotate the globe around the third (previously fixed) axis using right click and drag. Unfortunately, this is very easy to trigger accidentally when trying to open the context menu. And there is no option to disable this annoying feature.

Please either change the trigger for this to something not so easy to accidentally trigger (maybe left-click with some modifier?), or make the feature optional, or both.

Comment 1 Kevin Kofler 2018-01-29 00:54:10 UTC

Note that this is all the more annoying because there is no usable way to undo the rotation, see bug #389579.

Comment 2 Kevin Kofler 2018-02-18 22:36:38 UTC

Ping? Am I really the only one annoyed by this? Maybe my mouse is just not precise enough, but it's almost impossible to right-click on the map without moving the mouse cursor by a pixel or two, which immediately triggers this rotation mode. Maybe there should be at least a minimum moving distance before initiating the rotation.

(I also have not received any answer to my other 3 reports of regressions caused by this new feature.)

Comment 3 Christoph Feck 2018-03-01 02:55:20 UTC

Drag should only initiate when either QApplication::startDragDistance() or QApplication::startDragTime() is reached.

The LMB button handling checks d->m_dragThreshold, the new RMB button handling does not.

Comment 4 Kevin Kofler 2022-01-09 06:19:58 UTC

Marble from KDE Applications 20.12.2 (still claims to be version 2.2.20) now finally has an option that allows this to be disabled.