lol, must look like i have some kind of mouse fetish with these threads huh?
anyway i didn't want to change the subject of my previous thread so instead i'll post a fresh one:
seems when i call movemouse() and then initiate the main loop where a condition checks the location of the mouse, the condition returns the co-ords prior to the movemouse being called! all i can assume here is that mouse movement is asynchronous to command execution. easy fix would be to whack a delay between these events, but i'm somewhat of a freak when it comes to making clean code, and delays always look messy to me...
please note i've already played around with pollsystem() to no avail!
system in question is gnu linux 2.6.11 running fedora 4 (flame fc all ye like, but personally i love it!), xorg 6.8.2, and the logitech mx1000 mouse. blitzmax build is 1.08.
script in question:
HideMouse()
MoveMouse half_width, half_height
While (GetChar() + MouseHit(1) + MouseHit(2) + MouseHit(3) + MouseZ() = 0) And MouseX() = half_width And MouseY() = half_height
ty.
anyway i didn't want to change the subject of my previous thread so instead i'll post a fresh one:
seems when i call movemouse() and then initiate the main loop where a condition checks the location of the mouse, the condition returns the co-ords prior to the movemouse being called! all i can assume here is that mouse movement is asynchronous to command execution. easy fix would be to whack a delay between these events, but i'm somewhat of a freak when it comes to making clean code, and delays always look messy to me...
please note i've already played around with pollsystem() to no avail!
system in question is gnu linux 2.6.11 running fedora 4 (flame fc all ye like, but personally i love it!), xorg 6.8.2, and the logitech mx1000 mouse. blitzmax build is 1.08.
script in question:
HideMouse()
MoveMouse half_width, half_height
While (GetChar() + MouseHit(1) + MouseHit(2) + MouseHit(3) + MouseZ() = 0) And MouseX() = half_width And MouseY() = half_height
ty.