In HC, I always distinguished, within a single mouseUp handler, the
difference between a single mouseClick and a double mouseClick as:
on mouseUp
wait 15
if the mouseClick then put "Double" else put "Single"
end mouseUp
But it seems more modern, more revLike, to use a mouseUp handler and a
On Tue, Aug 10, 2010 at 11:22 PM, wrote:
> In HC, I always distinguished, within a single mouseUp handler, the
> difference between a single mouseClick and a double mouseClick as:
>
> on mouseUp
> wait 15
> if the mouseClick then put "Double" else put "Single"
> end mouseUp
>
> But it seems m
zryip-
Tuesday, August 10, 2010, 3:36:24 PM, you wrote:
> Have a look to this old thread:
> http://www.mail-archive.com/use-revolution@lists.runrev.com/msg110620.html
Ah... Eric to the rescue once again...
--
-Mark Wieder
mwie...@ahsoftware.net
__
On Wed, Aug 11, 2010 at 12:40 AM, Mark Wieder wrote:
> zryip-
>
> Tuesday, August 10, 2010, 3:36:24 PM, you wrote:
>
>> Have a look to this old thread:
>
>> http://www.mail-archive.com/use-revolution@lists.runrev.com/msg110620.html
>
> Ah... Eric to the rescue once again...
>
The master is away b
On 8/10/10 5:40 PM, Mark Wieder wrote:
zryip-
Tuesday, August 10, 2010, 3:36:24 PM, you wrote:
Have a look to this old thread:
http://www.mail-archive.com/use-revolution@lists.runrev.com/msg110620.html
Ah... Eric to the rescue once again...
Ken Ray had a good one too, a long time ago.
I was going to post something on those lines too (the one where you set a
variable to know whether to not do the mouseup after all), but there's a big
problem. The rules for mousedoubleup are that it is triggered when the mouse is
released after the double click. That means you could click, clic
Controls that take different behaviors based on whether a single- or
double-click has been received often limit the single-click behavior to
selection, but reserve any action for the double-click.
For example, you may have an Inspector that updates when an object is
single-clicked, but double-
