Flow.Launcher
Flow.Launcher copied to clipboard
BUG: Wrong positioning on multimonitor setup
Checks
-
[X] I have checked that this issue has not already been reported.
-
[X] I am using the latest version of Flow Launcher.
Problem Description
I have a multi monitor setup with two screens 1920x1200 (screen 1) and 1900x1080.
On monitor 2 the following settings for the window position on monitor result in the search bar being shown on monitor 1...
- ...on the right top for center top
- ...on the left top for left top
- ...not at all for right top (however the current window looses focus -> its probably displayed out of bounds)
To Reproduce
- Configure setting
- Set window position to custom monitor 2 (the same happens for monitor for mouse cursor or monitor with focused window)
- Hit alt+enter
Screenshots
No response
Flow Launcher Version
1.16.1
Windows Build Number
10.0.22621.2134
Error Log
Nothing gets added to the logs.
Replace this line with the important log contents.
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Hello, https://ci.appveyor.com/project/JohnTheGr8/flow-launcher/builds/49954411/artifacts Please grab the portable version from the link above, give it a try, and let us know if it solves your problem.
Yes, it does. Thank you very much!
@onesounds Has this issue been resolved?
Idk. I tried working on it but ended up giving up. I’m pretty sure someone else handled it, but I’m not exactly sure.
Ah, I remember now. I initially fixed it, but Taoo later reworked it using Point2D, which caused some issues. Taoo stopped working on it afterward, and since I wasn’t familiar with Point2D, I couldn’t fix it myself. Eventually, I had to roll back all the changes to get ready for the release.
Ah, I remember now. I initially fixed it, but Taoo later reworked it using Point2D, which caused some issues. Taoo stopped working on it afterward, and since I wasn’t familiar with Point2D, I couldn’t fix it myself. Eventually, I had to roll back all the changes to get ready for the release.
So, the current version should have fixed this issue. And can we close this issue?
Oh no. Tao has directly edited your PR😢, so the fix is reverted finally.
Nice, thank you all!