-
Notifications
You must be signed in to change notification settings - Fork 279
fix: Window opening on dual screen #1183 #1213
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
Conversation
It looks reasonable to me. @mmstick what do you think? |
I would recommend squashing this into one commit, though |
How to squash this into one commit? |
Do I need to delete repo, fork this repo and make changes in one commit? |
As long as QA is okay with the window attaching to the display that the mouse is on, regardless of which window is actively focused. Because GNOME always opens the window on the display where the mouse is. |
Is this what I needed to do? |
Or do I need to do this with every commit? |
Now you have more commits rather than less |
Sorry |
So what do I need to do? More precisely please. I'm 14. |
I believe you can get what is needed with the following:
|
After |
Nope, you should be seeing the files you modified. What are your remotes looking like?
|
|
I see the issue. You need to do as follows:
|
Spotify Flatpak returns `null` for `meta.get_title()`. Use window name instead.
Why are in the commit changes that I didn't do? |
It looks like those are the changes to our local master branch which you had previously merged in as a merge commit. It shouldn't be a problem, provided the Engineering review still checks out. |
The description for the commit is talking about the Flatpak fix and not what this commit's actually doing. |
I squashed the commits from earlier into the correct starting commit and force-pushed. The metadata should be correct now, will test soon. |
So, that's it? |
After building this locally to test, this doesn't seem to fix #1183: simplescreenrecorder-2021-10-14_15.34.02.mp4At first, I thought it was because of the mouse position behavior that @mmstick described, but I also recreated it where the window gets fullscreened onto a display the mouse isn't on: simplescreenrecorder-2021-10-14_15.38.54.mp4 |
Is working, except if there are more than two windows on second display and zero on main, then Minecraft 1.17 moves to main display. Minecraft 1.8 moves to main display every single time. Fix is not perfect but it's better than nothing (for me). How are your videos long 30s and less than 10MB and mine 15s and 15MB? |
Now should work with Minecraft 1.17 but not with Minecraft 1.8 |
3a520dc
to
ee60b64
Compare
I'm still not seeing any change in behavior, still testing with Minecraft 1.17 since it's the latest version: The window and cursor were both on the primary display, then Minecraft full-screened itself to the external display. We're wanting it to full-screen onto the same display it's currently on, correct? |
If you press F11 three times is working... |
The only change this makes is reverting 49aba22 |
Yes... |
Commit was reverted, so we can close this |
I have no idea what I changed, but now is working perfectly!