Hey guys! K.... heres the problem:<br><br>I'm using interrupts to get a high screen resolution (works fine), but I'm using absolute for the mouse. I've tested both and they work fine individually, but when I combine them it seems that the '$include 'qb.bi' frigs up the absolute... but if I remove the absolute it frigs up the interrupts.....<br><br>Is there a way to do mouse using interrupts or is there a way to do the screen using absolute OR is there a way to allow both to work in the same program by adding or removing some code????<br><br><br>Thanks<br><br>Daniel Brown
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Absolute and Interrupts
- Thread starter dbrown83
- Start date
Here's how to use the mouse:<br><FONT FACE=monospace><b><br>DEFINT A-Z<br>TYPE RegTypeX<br> AX AS INTEGER<br> BX AS INTEGER<br> CX AS INTEGER<br> dx AS INTEGER<br> bp AS INTEGER<br> si AS INTEGER<br> di AS INTEGER<br> FLAGS AS INTEGER<br> DS AS INTEGER<br> ES AS INTEGER<br>END TYPE<br><br>DECLARE FUNCTION MouseInit ()<br>DECLARE SUB Mousemove (mRow, mCol)<br>DECLARE SUB MouseShow ()<br>DECLARE SUB MouseHide ()<br>DECLARE SUB GetMouse (Click, MouseRow, MouseCol)<br><br>SUB GetMouse (Click, MouseRow, MouseCol) STATIC<br>DIM InRegs AS RegTypeX, OutRegs AS RegTypeX<br>InRegs.AX = 3<br>CALL INTERRUPTX(&H33, InRegs, OutRegs)<br>Click = 0<br>C = OutRegs.BX<br>IF C <> 0 THEN<br> MouseDown = C<br>ELSE<br> IF MouseDown <> 0 THEN<br> Click = MouseDown<br> MouseDown = 0<br> END IF<br>END IF<br>MouseRow = OutRegs.dx \ 16 + 1<br>MouseCol = OutRegs.CX \ 8 + 1<br>END SUB<br><br>SUB MouseShow<br> DIM InRegs AS RegTypeX, OutRegs AS RegTypeX<br> InRegs.AX = 1<br> CALL INTERRUPTX(&H33, InRegs, OutRegs)<br>END SUB<br><br>SUB MouseHide<br> DIM InRegs AS RegTypeX, OutRegs AS RegTypeX<br> InRegs.AX = 2<br> CALL INTERRUPTX(&H33, InRegs, OutRegs)<br>END SUB<br><br>FUNCTION MouseInit<br> DIM InRegs AS RegTypeX, OutRegs AS RegTypeX<br> InRegs.AX = 0<br> CALL INTERRUPTX(&H33, InRegs, OutRegs)<br> MouseInit = OutRegs.AX<br>END FUNCTION<br><br>SUB Mousemove (mRow, mCol)<br>DIM InRegs AS RegTypeX, OutRegs AS RegTypeX<br> InRegs.dx = 16 * (mRow - 1) '8 * (mRow - 1)<br> InRegs.CX = 8 * (mCol - 1)<br> InRegs.AX = 4<br> CALL interrupt(&H33, InRegs, OutRegs)<br>END SUB<br></font></b><br><br>Use MouseInit to initialize the mouse driver.<br>Use MouseHide before you make changes to the screen and then use MouseShow immediately after.<br>Use MouseMove if you want to move the mouse cursor to a certain screen location.<br>Use the GetMouse sub to return the location of the mouse cursor and whether or not it was clicked. This sub should be in any loop that waits for user input.<br><br>Have fun. I hoped this solved your problem.<br><br>BTW, you might want to eliminate the QB.BI "include" and place everything in your modules. (I've had fewer problems that way.)<br><br><br><br> <p> <br><a href=mailto: > </a><br><a href= plain black box</a><br>
Oops, the integer division by 16 and 8 in the MouseMove and GetMouse subs are set to return the relative "text" coordinates. If you are using a graphic screen larger than 640x480 you will have to play with those values to return the correct cursor coordinates.<br><br>Sorry about that. I don't have any conversion tables on hand to post.<br> <p> <br><a href=mailto: > </a><br><a href= plain black box</a><br>
- Status