ah, you have a point there. but is there any way to make qb64 "itself" take on your loop?

by mennonite (no login)

obviously, things like getmouse and inkey$ need to be in a loop to be useful, but they don't typically need to be in a loop until theinput=0, you know?

don't think i'm not happy with _mousex _mousey and _mousebutton, i am. it's so much nicer than learning asm. i just think it could be better, and you're still changing it, so i thought i'd mention it for the sake of that thing we both care about, the basicness of basic.

Posted on Jun 2, 2008, 4:15 AM
from IP address 85.195.119.22

Respond to this message   

Return to Index


Response TitleAuthor and Date
Perhaps a dofferent approach might help here. on Jun 2
 that wouldn't actually make any dofferencemennonite on Jun 2
Imagine surfing the net, but every third click your mouse didn't work... on Jun 2
 there's a one way understanding heremennonite on Jun 2
  here is how getmouse worksmennonite on Jun 2
   And this is why getmouse is bad... on Jun 2
    Wouldn't CALL INTERRUPT 33 also have that problem? on Jun 2
    but inkey$ will capture the esc keypress...mennonite on Jun 2
     totally plain and concise english is not my first language, it takes a while....mennonite on Jun 2
      I understand exactly what you are saying Mennonite on Jun 3
       i'll have to concede for practical reasons thenmennonite on Jun 3
        There's no reason you couldn't code your own "getmouse" routine on Jun 3
         isn't mousewheel just a button that you can click over and over?mennonite on Jun 3
          oh except that it is also a button, not just a wheelmennonite on Jun 3
           RE: Isn't the mouse wheel just a button? on Jun 4
            * Wouldn't ABSOLUTE and INTERRUPT code ignore that? on Jun 4
            *More mouse buttons than the normal 3? Oh! Those fancy ones with Back/Forward buttons? :-Prpgfan3233 on Jun 4