Skip to content
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

Wrong offset of the GB display when started from the command line with mgba-qt #843

Closed
linkmauve opened this issue Aug 4, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@linkmauve
Copy link
Contributor

commented Aug 4, 2017

When I start a GB game by clicking File > Load File, everything is rendered correctly, but when I start it by giving its path as the first argument to mgba-qt it has a small offset which doesn’t change on resize.

Here is a screenshot demonstrating the first case (left) and the bug (right):
wayland-screenshot

This is running 0.6.0 from the ArchLinux community repository, using X11.

@endrift

This comment has been minimized.

Copy link
Member

commented Aug 4, 2017

Hmmm haven't seen this before, and I'm pretty sure it doesn't happen in master. Can you install mgba-qt-git from AUR and see if it reproduces?

@linkmauve

This comment has been minimized.

Copy link
Contributor Author

commented Aug 4, 2017

I can actually reproduce on 0.7-6-40fb750, and also on Wayland.

@endrift

This comment has been minimized.

Copy link
Member

commented Aug 4, 2017

weiiiird, because I CAN'T reproduce it on macOS. Will reboot into Arch shortly.

I can reproduce what is probably the same issue on Windows and I am having a problem on macOS but it's an ancient bug I've never been able to solve--might be the same bug.

@endrift

This comment has been minimized.

Copy link
Member

commented Aug 4, 2017

I can't reproduce this on Arch, but I've solved the Windows bug. The patch only applies to master though so I'll work on one for 0.6 branch too.

@endrift endrift closed this in 30db4eb Aug 4, 2017

@endrift

This comment has been minimized.

Copy link
Member

commented Aug 4, 2017

Please confirm this fix on master. I'm having trouble making a version that applies to 0.6, so I might need to pass that up for 0.6.1 unfortunately.

@linkmauve

This comment has been minimized.

Copy link
Contributor Author

commented Aug 4, 2017

I confirm it works properly on master now, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.