Message order of mouseUp and mouseDoubleUp

[dunbarx at aol.com]

Bob.


The problem is two separate actions that are rather too intimately married; "mouseUp" and "mouseDoubleUp".


The engine is just not discriminating these reliably, and in a way, I cannot blame it. To work unambiguously, it would have to always wait for the doubeClickInterval to time out to determine what the user really wanted. This would work, I guess, but would cause a delay in response for every single click for an ordinary "mouseUp". This would be quite noticeable.


The HC way, old fashioned though it is, is best.


Craig Newman








-----Original Message-----
From: Bob Sneidar <bobs at twft.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Mon, Jun 4, 2012 12:35 pm
Subject: Re: Message order of mouseUp and mouseDoubleUp


Are you handling MouseUp somewhere else in the message path? If not, then just 
let it pass. 

Bob


On Jun 3, 2012, at 7:40 PM, Bill Vlahos wrote:

> I have a button that has handlers for mouseUp and mouseDoubleUp. If the user 
double clicks the button the mouseUp always gets handled before the 
mouseDoubleUp.
> 
> How can I prevent that? If the user double clicks I only want the 
mouseDoubleUp message to be sent or at least be sent before the mouseUp.
> 
> Bill Vlahos
> _________________
> InfoWallet (http://www.infowallet.com) is about keeping your important life 
information with you, accessible, and secure.
> lcTaskList: (http://www.infowallet.com/lctasklist/index.htm)
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode