QB64.org Forum
Active Forums => QB64 Discussion => Topic started by: TempodiBasic on March 04, 2020, 09:06:30 am
-
Hi guys
there is an option to disable the stack of mouse informations without using use _MOUSEINPUT in a loop until it returns 0.
?
Reference https://www.qb64.org/wiki/MOUSEINPUT#Syntax (https://www.qb64.org/wiki/MOUSEINPUT#Syntax)
-
Well, no.
-
thanks to stop me to waste time to avoid that stack... :-)
Well I must re-think the performance introducing the canonical .
-
Hi TempodiBasic,
What are you attempting to achieve?
The oldMouse trick is good for distinguishing a new mouse down from the last, I first saw from Steve, works well and pretty simple.
And if you are testing mouse routines, I am sure curious about seeing Terry's tested in more situations:
https://www.qb64.org/forum/index.php?topic=2195.0
-
What are you attempting to achieve?
just I'm going on with the idea to shrink the initial codeloop of Krovit...
why? It was a challange to me to achieve a mouse manager with one loop... just to think different and not to think doing better than previous examples of code posted.
And I got a one loop with echo of the one click event after a dragging and / or doubleclick event! :-)
After looking at variables initialization with tedious and verbose printing on the screen I see that also resetting variables
the parser of mouse events takes again inputs from mouse also if there was no more input... so the stack of mouse input is the only reason for getting this experience...