reckes / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

Cursor won't hide in fullscreen mode #187

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Describe your system:
- Linux distribution:
- Machine type: (32-bit or 64-bit)
- Mupen64Plus version:
- Plugins used:

For visual artifacts, give:
- game name and CRC/MD5 hash (printed on console)
- description of the artifact (missing polygons, flashing, wrong colors, etc)

Describe the problem:

Just got mupen64+, and I love it - HOWEVER:
Whenever I run any roms in fullscreen, my mouse pointer stays in the dead
center of the screen, and I can't move it or get it to hide or anything.

Please provide any additional information below.

Original issue reported on code.google.com by slappe...@gmail.com on 30 Dec 2008 at 12:27

GoogleCodeExporter commented 8 years ago
This is a system problem.  The Mupen64Plus code calls the SDL function for 
disabling
the mouse pointer, so if it's not working then you have a problem with SDL or
Gnome/KDE, X-windows, etc.  If you give all the system details (which are 
prompted
for at the beginning of this issue report) someone may be able to help you 
further.

Original comment by richard...@gmail.com on 30 Dec 2008 at 7:01

GoogleCodeExporter commented 8 years ago
Forgive me - I suppose I submitted my problem to quickly.

Describe your system:
- Linux distribution: Ubuntu Intrepid Ibex
- Machine type: (32-bit or 64-bit) Dell inspiron e1405 32 bit
- Mupen64Plus version: 1.4.1
- Plugins used: Rice's Video Plugin 1.4.1, JttL SDL Audio 1.4.1, blight's SDL 
input
plugin 0.0.10, Hacktarux/Azimer hle rsp

Any help is appreciated

Original comment by slappe...@gmail.com on 30 Dec 2008 at 8:15

GoogleCodeExporter commented 8 years ago
Are you using compiz (desktop 3D effects)?

Original comment by richard...@gmail.com on 30 Dec 2008 at 9:57

GoogleCodeExporter commented 8 years ago
This issue report is over a year old and the original reporter didn't reply to 
my
last question.  Since no-one else reported the same problem, I assume this was a
system issue.

Original comment by richard...@gmail.com on 12 Jan 2010 at 5:35