Editor should fall back to primary monitor when it can't choose the biggest one · Issue #242 · focus-editor/focus · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I double-click the .exe it opens on my secondary monitor, not my primary monitor. If I move it to my primary monitor, then close it, and re-open it, it's still on my secondary monitor.
Expected behavior
I expect it to:
open on my primary monitor by default
and
to re-open wherever I last left it if I've opened it previously and re-positioned it (assuming the saved location is still valid).
(1) is much easier and should be a fast fix.
(2) is more of a feature request at your discretion.
OS: Windows 11
Focus Version: focus-nightly-f0730db.exe
The text was updated successfully, but these errors were encountered:
For (1) you probably have open_on_the_biggest_monitor: true in your config. Please have a look at the other options in the config as there might be some other surprising things in there as well.
Both of my monitors are the exact same model and resolution, 1080p. They're set up in a standard side-by-side configuration. I wouldn't expect a setting called "biggest monitor" to have any effect at all on which one gets chosen.
Setting it to false does indeed solve the problem, thanks.
focus-editor
changed the title
Editor opens on wrong display
Editor should fall back to primary monitor when it can't choose the biggest one
Dec 23, 2023
Describe the bug
When I double-click the .exe it opens on my secondary monitor, not my primary monitor. If I move it to my primary monitor, then close it, and re-open it, it's still on my secondary monitor.
Expected behavior
I expect it to:
and
(1) is much easier and should be a fast fix.
(2) is more of a feature request at your discretion.
The text was updated successfully, but these errors were encountered: