Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,005 of 4,675    |
|    wolfgang kern to Jens Kallup    |
|    Re: programming on PS2 mouse controller    |
|    29 Sep 17 20:13:45    |
      From: nowhere@never.at              Jens Kallup wrote:              > Hello Wolfgang,              Hi,              > can it be, that I have to draw the the       > MOUSEX, and MOUSEY by myself?              Yes of course, who else would know where your mouse is ?              > I hope these are screen coordinates?              the mouse reported X/Y values are only motion infos.              > MOUSE x/y -> where to get/set the position?              I'd start with top-left (00 00) and then add/sub the reported values to       it but also clamp it to the actual visible range to keep it on screen.              Of course you need to know the line length and max.rows       for the current used screen mode.              And there is a big difference between text-mode and graphic-mode.              In text mode you can alter the attribute byte, while in graphic-mode you need       to either use a hardware mouse image or draw one self defined.              Again, dont forget to save and restore the original at the previous POS       to make the mouse movable without overwriting everything.       __       wolfgang              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca