https://bugs.winehq.org/show_bug.cgi?id=44417
Bug ID: 44417 Summary: WINE Does Not Detect Primary Display Correctly on macOS Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs@winehq.org Reporter: me@haravikk.com
The title mostly says it all with this one; while WINE detects both of my displays at the correct resolution etc., it unfortunately doesn't get them in the right order, which can be annoying with games that don't offer a choice of which screen to use when running in fullscreen mode. Usually there's a workaround, but in some cases there is not.
To give some detail; my machine has two monitors, one is a 1680x1050 monitor attached via DVI, and the other is a 1080p screen attached via HDMI. It seems that the DVI connection is considered the primary screen by the GPU, so it has to be overridden under System Preferences -> Displays to reclassify which is the primary display.
While it's understandable that WINE would likewise prioritise the DVI screen first, it would be nice if it could use the system's display configuration to reorder the displays.
Searching online the impression I got is that this may be what happens under a Linux host, but it doesn't seem to occur under macOS.
While there may be an API call that can do this more easily, the information can be obtained from a user's ~/Library/Preferences/ByHost/com.apple.windowserver.<machine_uuid>.plist file, where <machine_uuid> is the UUID used to identify the machine itself, though I'm not certain what value indicates which display is the primary one, or if it's simply the order in which they are provided (i.e- primary first).
Anyway, if WINE's method of obtaining the display information could be changed to either get them in the order as defined by macOS's Display settings, then this would be great.
https://bugs.winehq.org/show_bug.cgi?id=44417
me@haravikk.com me@haravikk.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64
https://bugs.winehq.org/show_bug.cgi?id=44417
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ken@codeweavers.com
--- Comment #1 from Ken Thomases ken@codeweavers.com --- How exactly did you specify the primary display in System Preferences > Displays? Also, do you have System Preferences > Mission Control > "Displays have separate Spaces" enabled?
https://bugs.winehq.org/show_bug.cgi?id=44417
--- Comment #2 from me@haravikk.com me@haravikk.com --- Under System Preferences -> Displays -> Arrangement I repositioned the smaller display, and moved the menubar from it over to the larger display (Apple really needs to change this now that all displays get a menubar).
And yes, I have displays configured with separate Spaces.
https://bugs.winehq.org/show_bug.cgi?id=44417
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|wineserver |-unknown
--- Comment #3 from Ken Thomases ken@codeweavers.com --- (In reply to me@haravikk.com from comment #2)
Under System Preferences -> Displays -> Arrangement I repositioned the smaller display, and moved the menubar from it over to the larger display (Apple really needs to change this now that all displays get a menubar).
OK, good.
And yes, I have displays configured with separate Spaces.
I don't generally have that enabled. It's possible it interferes with the detection of the primary display.
Are you using Wine's Mac driver or its X11 driver? What version of Wine? What version of macOS?
In general, the Mac driver should respect the primary display as selected in System Preferences, and does in my testing.
https://bugs.winehq.org/show_bug.cgi?id=44417
--- Comment #4 from me@haravikk.com me@haravikk.com ---
Are you using Wine's Mac driver or its X11 driver? What version of Wine? What version of macOS?
I've been using the Mac driver (it usually runs better), and macOS 10.13.3.
The most recent WINE version I've tried is v3.0 (rc6), but the issue also occurs on v2.22 which is the one I've been using for most things. I tend to run WINE through either PlayOnMac or Wineskin, since they make it a lot easier to run things from one version of WINE and then periodically try something more recent to see if it resolves issues/improves performance.