Multiple-click events

[kimtopley at gmail.com]

> It seems a little dangerous to arbitrarily delay all initial mouse clicks. 

Or at least inconvenient for applications that don't want this feature, which is why I think it would be useful to have an "opt in" rather than force the delay on everybody.

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Jeff Martin <jeff at reportmill.com>
Date: Fri, 27 Apr 2012 10:51:17 
To: <kimtopley at gmail.com>
Cc: Pavel Safrata<pavel.safrata at oracle.com>; <openjfx-dev-bounces at openjdk.java.net>; openjfx-dev at openjdk.java.net<openjfx-dev at openjdk.java.net>; Alexander Kouznetsov<alexander.kouznetsov at oracle.com>; VIENOT, SIMON<simon.vienot at oracle.com>; Richard Bair<Richard.Bair at oracle.com>
Subject: Re: Multiple-click events

It seems a little dangerous to arbitrarily delay all initial mouse clicks. Does Swing do anything like this? I've never run into a problem with processing both single and double clicks, but if it was an issue, isn't there some kind of event peek that could easily be done:

	if(mouseEvent.getClickCount()==1) {
		Thread.sleep(200);
		if(EventDispatcher.peek(MouseEvent.MOUSE_CLICKED!=null) return;
		< … handle single click normally … >
	}

If that isn't there, could that be added instead?

jeff


On Apr 27, 2012, at 10:23 AM, kimtopley at gmail.com wrote:

> Would it be possible to make this configurable, maybe at the Scene level? In some cases, a single click is all that's required and the delay waiting for a second click that means nothing more to the application is unnecessary. 
> 
> 
> Sent from my Verizon Wireless BlackBerry
> 
> -----Original Message-----
> From: Pavel Safrata <pavel.safrata at oracle.com>
> Sender: openjfx-dev-bounces at openjdk.java.net
> Date: Fri, 27 Apr 2012 17:17:10 
> To: openjfx-dev at openjdk.java.net<openjfx-dev at openjdk.java.net>
> Cc: VIENOT, SIMON<simon.vienot at oracle.com>; Alexander Kouznetsov<alexander.kouznetsov at oracle.com>; Richard Bair<Richard.Bair at oracle.com>
> Subject: Multiple-click events
> 
> Hello,
> currently we deliver MOUSE_CLICKED event any time a node was pressed and 
> released by mouse; if the next press happens fast enough and near 
> enough, we increase the clickCount number for the events. There are 
> requests to make a standalone single-click distinguishable from a first 
> click of a double-click (and so on).
> 
> After some discussion we concluded that the cleanest approach would be 
> somewhat backward incompatible - we propose to generate the click event 
> only when we are sure that there is no next click. In other words, the 
> partial clicks would not be delivered at all, the final click would be a 
> bit delayed. The pressed/released events would of course be still 
> delivered normally, with the correct clickCount value.
> 
> Any objections?
> 
> Thanks,
> Pavel
>