Pharo Issue Tracker - Manuscript (Case [Issue]22648) Morphic - spaced double-click misinterpreted as start drag event

Manuscript Notification

	Stephan Eggermont revised a previous entry on Case 22648: spaced double-click misinterpreted as start drag event: Bug in Morphic: 1. Pharo Image • You are subscribed to this case

I first observed this problem in Naut u i lus in Pharo 6.1 by quickly subsequently clicking on two different methods, which results in a drag action of the first clicked method.

This behaviour is initiated in MouseClickState>>handleEvent: evt from: aHand

This problem can be resolved by removing "self drag: firstClickDown" under the branch clickState == #secondClickDown.

I cannot imagine that a second click can ever be the start of drag event?

Stephan Eggermont's reply in discord:

There doesn't seem to be enough test coverage there, and the behaviour seems incorrect. It is also present in Pharo 7 in Calypso

The method is too long , and the class is in the wrong place. It has something to do with event handling, not a progressbar.

I'd guess Morphic-Base-Events would be a better place

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Later

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker