I have added this but it does not help. I then comment "mouse IMPS2" line but it does not help too. I assume svgalib doesn't need to be recompiled to the changes take effect. Jacek Hi , Please add mouse PS2 in the config file Regards, Hemanth Jacek Kurzyca <gepardzik@o2.pl> wrote:You can find my libvga.config file here: http://blackhole.ovh.org/files/libvga.config Jacek
U doesn't need to recompile comment the line mdev /dev/psaux
Hemanth
Jacek Kurzyca gepardzik@o2.pl wrote: I have added this but it does not help. I then comment "mouse IMPS2" line but it does not help too.
I assume svgalib doesn't need to be recompiled to the changes take effect.
Jacek Hi , Please add
mouse PS2
in the config file
Regards, Hemanth
Jacek Kurzyca gepardzik@o2.pl wrote:You can find my libvga.config file here: http://blackhole.ovh.org/files/libvga.config
Jacek
--------------------------------- Find out what India is talking about on - Yahoo! Answers India Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
Jacek Kurzyca wrote:
I have added this but it does not help. I then comment "mouse IMPS2" line but it does not help too. I assume svgalib doesn't need to be recompiled to the changes take effect.
You said the mouse in mousetest works fine. I suppose that's with the same configuration (svgalib etc.), so I think it's unlikely that it's the svgalib settings.
I know where my program crashes. It's when I run GrMouseEvent(GR_M_EVENT,&evt);
(I suppose you mean GrMouseGetEvent.)
and moved mouse while this function's running. If I click mouse button program goes on. It crashes only after mouse move.
Have you checked this with gdb? Can you send a backtrace ("bt" in gdb) of the crashed program?
(You know, the fact that it crashes after mouse movement doesn't necessarily mean that it crashes in GrMouseGetEvent. It could also be an error elsewhere in your program, in the code that's executed after mouse movement, or something else.)
Frank
(I suppose you mean GrMouseGetEvent.)
Yes.
and moved mouse while this function's running. If I click mouse button program goes on. It crashes only after mouse move.
Have you checked this with gdb? Can you send a backtrace ("bt" in gdb) of the crashed program?
I had just checked this with gdb. In gdb my program do nothing when I moved the mouse.
(You know, the fact that it crashes after mouse movement doesn't necessarily mean that it crashes in GrMouseGetEvent. It could also be an error elsewhere in your program, in the code that's executed after mouse movement, or something else.)
I've added getch() after GrMouseGetEvent and when I moved mouse (not in gdb) then program crashes, getch() isn't issued and on console I receive a message:
--------------------- svgalib 1.4.3 svgalib: Failed to initialize maouse. rivafb_open START
rivafb_release END ---------------------
Frank
Jacek
Jacek Kurzyca wrote:
I've added getch() after GrMouseGetEvent and when I moved mouse (not in gdb) then program crashes, getch() isn't issued and on console I receive a message:
svgalib 1.4.3 svgalib: Failed to initialize maouse. rivafb_open START
rivafb_release END
I discover now this message is displayed before I change graphics to 1024x768x256c. I've wrote test code:
GrSetMode(...); getch(); // mouse init function is far away after this code
And if I click Ctrl-C while program's waiting for a key, program exits and above message is visible on the screen (text mode).
Jacek
Jacek Kurzyca wrote:
Jacek Kurzyca wrote:
I've added getch() after GrMouseGetEvent and when I moved mouse (not in gdb) then program crashes, getch() isn't issued and on console I receive a message:
svgalib 1.4.3 svgalib: Failed to initialize maouse. rivafb_open START
rivafb_release END
I discover now this message is displayed before I change graphics to 1024x768x256c. I've wrote test code:
GrSetMode(...); getch(); // mouse init function is far away after this code
And if I click Ctrl-C while program's waiting for a key, program exits and above message is visible on the screen (text mode).
Well, we can keep on guessing, but I don't think that's very efficient. As I wrote, showing some code or at least a backtrace might help ...
Frank
Well, we can keep on guessing, but I don't think that's very efficient. As I wrote, showing some code or at least a backtrace might help ...
Frank
My program works fine :) Mouse wasn't the reason of that problems. It was a mistake in my code.
Thanks for all!
Jacek
-
"Jacek Kurzyca" -
Frank Heckenbach -
Frank Heckenbach -
Hemanth Kumar