Re: extra mousedown messages
On Wed, 2 May 2007 11:15:21 +0200, Wouter wrote: > > in rev 2.1: > mousedown button "Button 1" 1178096229057 > mousedoubledown button "Button 1" 1178096229203 > mousedoubledown card id 1002 1178096229208 > --> mouse released : no further messages > > in rev 2.5.1: > mousedown button "Button" 1178096730853 > mousedoubledown button "Button" 1178096731000 > mousedoubledown card id 1002 1178096731013 > --> mouse released --> > mousedown button "Button" 1178096731733 > > in rev 2.8.1 > mousedown button "Button" 1178096881969 > mousedoubledown button "Button" 1178096882131 > mousedoubledown card id 1002 1178096882145 > --> mouse released --> > mousedown button "Button" 1178096883161 > > Question: is this considered normal behavior? I wouldn't think so... having a mouseDown generated when the mouse is released sounds like a bug to me. Looks like the "Rev 2.1" did it right IMHO... Ken Ray Sons of Thunder Software, Inc. Email: [EMAIL PROTECTED] Web Site: http://www.sonsothunder.com/ ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: extra mousedown messages
Recently, Wouter wrote: > Having had some problems caused by extra messages generated in > certain cases, I started hunting them down. Just for the sake of argument, have you tried paring the mouseDown handlers with empty mouseUp/doubleMouseUp handlers? In my scripts, I've found that triggering mouseDoubleDown and mouseDoubleUp is sometimes unreliable if the down state is not paired with the up state. Perhaps this is part of the issue you appear to have found. Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
extra mousedown messages
Hi All, Having had some problems caused by extra messages generated in certain cases, I started hunting them down. For this I used the following recipe: - create a mainstack and add a push button and a field with locktext true. - set the script of the card or the stack to: on mousedown if the optionkey is down then put "" exit to top end if put "mousedown" && the target && the millisecs & cr after msg end mousedown on mousedoubledown put "mousedoubledown" && the target && the millisecs & cr after msg end mousedoubledown - try performing a mousedubbledown and keep the mouse down - then release the mouse button and observe what happens Seemingly it gives the same results on Win32 and on MacOSX. I'll give the results with a push button: in rev 1.1: mousedown button "New Button 1" 1178096016059 mousedoubledown button "New Button 1" 1178096016178 --> mouse released : no further messages in rev 2.1: mousedown button "Button 1" 1178096229057 mousedoubledown button "Button 1" 1178096229203 mousedoubledown card id 1002 1178096229208 --> mouse released : no further messages in rev 2.5.1: mousedown button "Button" 1178096730853 mousedoubledown button "Button" 1178096731000 mousedoubledown card id 1002 1178096731013 --> mouse released --> mousedown button "Button" 1178096731733 in rev 2.8.1 mousedown button "Button" 1178096881969 mousedoubledown button "Button" 1178096882131 mousedoubledown card id 1002 1178096882145 --> mouse released --> mousedown button "Button" 1178096883161 Question: is this considered normal behavior? PS: this is not the only condition extra messages are generated. TIA. Greetings, Wouter ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
