Xref:	news-dnh.mv.net comp.os.msdos.djgpp:1374
Path:	news-dnh.mv.net!mv!news.sprintlink.net!sunic!sunic.sunet.se!news.lth.se!news.lu.se!ronneby.hk-r.se!news
From:	pt93mg AT pt DOT hk-r DOT se (Mats Grahm)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: grx mouse trouble
Date:	6 Aug 1995 15:53:26 GMT
Organization:	College University of Karlskrona-Ronneby
Lines:	64
Distribution:	world
References:	<mictaliDCsG96 DOT H1H AT netcom DOT com>
Reply-To:	pt93mg AT pt DOT hk-r DOT se
Nntp-Posting-Host:	thebe.pt.hk-r.se
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

> Mats Grahm (pt93mg AT pt DOT hk-r DOT se) wrote:
 
> [...] So I want to use the grx mouse
> : functions instead.
> 
> : But no luck. MouseDetect() returns true, and MouseEventMode(), MouseGetEvent()
> : and some other functions does not complain, although I'm not sure they do what
> : they should. But Some functions, like MouseInit() and MouseWarp() terminates
> : the program with the message "Internal error: invalid driver called".

In article H1H AT netcom DOT com, mictali AT netcom DOT com (Jere McDevitt) answers:

> I'd have to see exactly what your mouse functions are doing, however, I
> don't recall any type of standard mouse function MouseWarp.  Perhaps the
> mouse functions you are using were specific to a type of mouse driver that
> had extended capabilities.  The standard mouse functions are accessed
> through dos int 0x33.  If you'd like I'd be glad to mail you a list of the
> functions and simple C code (using int86 calls) that will give you all of
> the base functions.  I use this method as opposed to inline assembly
> language for portability reasons.

Thank's for responding! I'm getting a bit desperate now.

I use use only functions mentioned in LIBGRX user manual and prototyped in
<mousex.h>. MouseWarp(int, int) is one of them.

To try to isolate the problem, I tried the following simple test code:

#include <mousex.h>

main()
{
    MouseEvent event;
    if(MouseDetect()) {
	printf("Mouse detected\n");
	MouseEventMode(0);
	MouseInit();
	MouseDisplayCursor();
	MouseGetEvent(0, event);
	MouseEraseCursor();
	MouseWarp(0,0);
    }
}

These are the functions I primarily need for my real program.
	    
It compiles and links just fine. But MouseInit() terminates the program with the
message mentioned above. If I comment out that call (wich according to libgrx
manual is optitional anyway), I get the same error in the MouseWarp call.

I have another mouse library that just like the grx functions is little more
than wrapper functions to the int33 interface. They work fine with my standard
Microsoft mouse and mouse driver. But since grx mouse functions are sync'ed with
grx drawing primitives, I would rather use grx.
> 
> If you wan't to e-mail or post a copy of your mouse routines I'd be glad to
> look and make any suggestions I can.
> 
Thanks, I would appreachiate any help! From you or anyone else whom might have
an answer. So I post this rather than emailing.

Mats

- Raw text -