Author Topic: How Can I disable stack of mouse info?  (Read 3058 times)

0 Members and 1 Guest are viewing this topic.

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
How Can I disable stack of mouse info?
« on: March 04, 2020, 09:06:30 am »
Hi guys
there is an option to disable the stack of mouse informations without using
Quote
use _MOUSEINPUT in a loop until it returns 0.
?

Reference https://www.qb64.org/wiki/MOUSEINPUT#Syntax
Programming isn't difficult, only it's  consuming time and coffee

Marked as best answer by TempodiBasic on March 04, 2020, 04:17:52 am

FellippeHeitor

  • Guest
Re: How Can I disable stack of mouse info?
« Reply #1 on: March 04, 2020, 09:07:45 am »
Well, no.

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
Re: How Can I disable stack of mouse info?
« Reply #2 on: March 04, 2020, 09:21:19 am »
thanks to stop me to waste time to avoid that stack...  :-)
Well I must re-think the performance introducing the  canonical
Code: QB64: [Select]
.

Programming isn't difficult, only it's  consuming time and coffee

Offline bplus

  • Global Moderator
  • Forum Resident
  • Posts: 8053
  • b = b + ...
    • View Profile
Re: How Can I disable stack of mouse info?
« Reply #3 on: March 04, 2020, 11:52:41 am »
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

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
Re: How Can I disable stack of mouse info?
« Reply #4 on: March 04, 2020, 07:10:21 pm »
Quote
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...
Programming isn't difficult, only it's  consuming time and coffee