🚀 go-pugleaf

In article <1992Aug21.012808.14991@news.cs.brandeis.edu> dernis@binah.cc.brandeis.edu writes:
>In article <Bt2J9u.2t4@ecf.toronto.edu>, dhaliwa@ecf.toronto.ed
>u (DHALIWAL BIKRAM SINGH) writes:
>>I am having 
>>trouble with the computer drawing lines over the cursor.  I will draw a
>>line but when I move the cursor away, the line goes away.  
>>
>I am having a similar problem with the text cursor.  When I write
>under the cursor, either with BIOS or directly, moving the mouse, reveals 
>what was previously there.  Also scrolling with BIOS moves the mouse
>cursor, actually makes a copy deleting the cursor which appears when
>I move the mouse.
>
>It has occured to me that interrupt0x33function 0x0B, can be used with
>int 0x33 function 0x03, to write my own routines to control the
>cursor myself.  But I would have to poll it constantly, and intercepting
>int 0x21 wouldn't help because than I would have to write the whole
>driver from scratch.  So the function would just have to have a 
>polling loop.
>
>The same solution would work with a graphics cursor, but so much work to
>implement!
>
>Does someone know if there is an easier way?
>
>HELP!!!!
>Thanks,
>Mitch Dernis
>
>
The easiest way is to turn off the mouse cursor before writing anything to 
the screen.  You either have to integrate your screen display routines with
your mouse routines, or do it the hard way and manually turn off the mouse
cursor every time you write to the screen.

>
>>..............................................
>>: Bikram Dhaliwal (dhaliwa@civ.toronto.edu) : 
>>: Oakville        (dhaliwa@ecf.toronto.edu) :


Matt Smith
msmith@peruvian.utah.edu
Student - University of Utah Department of Computer Science