-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 7 mouse offset on 3.3.7 #451
Comments
Ok some update. For 3.3.7 on Windows 7, there is a fix. Right click on the EXE -> properties -> check " 'disable desktop composition" and the mouse will work properly. Not sure why it is happening and how it can be prevented. |
That is strange. There's probably a linker flags or option to the packager to set that. It might be related to the Theme setting. |
Is it possible to fix this for 3.3.7, as 3.3.8 performance is very very slow on Windows 10 :(. |
Sadly, I don't have the problem on my Win 7 virtual machine. Not the first time that VMs don't act like real machines - particularly for Graphics Cards and Drivers and I suspect that is where the problem lies. VM's default to very dumb graphics cards. Does your user have a more 'exotic` setup? There's not much we can do either way, except change the gtk3 version which is what shoes 3.3.8 does. That sets up a 'circular firing squad' for you. FYI, I was looking at Go and the Fyne GUI as a possible replacement for Gtk and ran into the graphics card issues for VMs - Fyne uses OpenGL MESA drawing and needs drivers setup up properly. Boo Hiss. |
Btw I cannot run Shoes 3.3.8 on Windows VM. Probably some driver thing. |
@ccoupe long one overdue but forget to open a ticket.
Some users reported issues with my app on Windows 7. The mouse button is offset to one side, just as it was happening on Windows 10 before but you manage to fix it.
A workaround is this -> Right click exe -> compatibility -> disable fullscreen optimization
I dont have windows 7 to test 3.3.8 but probably the issue is valid there.
I will set up a test W7 environment and let you know.
The text was updated successfully, but these errors were encountered: