- 06 May, 2016 1 commit
-
-
Ken Thomases authored
When this Retina mode is enabled and the primary display is in the user's default configuration, Wine gets told that screen and window sizes and mouse coordinates are twice what Cocoa reports them as in its virtual coordinate system ("points"). The Windows apps then renders at that high resolution and the Mac driver blits it to screen. If the screen is actually a Retina display in a high-DPI mode, then this extra detail will be preserved. Otherwise, the rendering will be downsampled and blurry. This is intended to be combined with increasing the Windows DPI, as via winecfg. If that is doubled to 192, then, in theory, graphical elements will remain the same visual size on screen but be rendered with finer detail. Unfortunately, many Windows programs don't correctly handle non-standard DPI so the results are not always perfect. The registry setting to enable Retina mode is: [HKEY_CURRENT_USER\Software\Wine\Mac Driver] "RetinaMode"="y" Note that this setting is not looked for in the AppDefaults\<exe name> key because it doesn't make sense for only some processes in a Wine session to see the high-resolution sizes and coordinates. Signed-off-by: Ken Thomases <ken@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
-
- 17 Nov, 2015 1 commit
-
-
Ken Thomases authored
winemac: Use the display unit number rather than display ID for the initial display mode registry key. On Macs with dual GPUs that automatically switch, the display ID is not stable. It changes when the active GPU changes. The resulted in the lookup of the initial display mode failing and games not being able to restore it properly. The display unit number should be more reliable, although still not perfect. Signed-off-by: Ken Thomases <ken@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
-
- 27 Oct, 2015 2 commits
-
-
Ken Thomases authored
The code had been checking the kDisplayModeDefaultFlag in the mode's IOFlags, but that doesn't do what I thought. That indicates which mode the driver considers to be the default for the hardware. It turns out there's no way to query the user's default mode. So, at the first opportunity during a given Wine session, the Mac driver queries the current display mode and assumes that's the user's default mode. It records that in a volatile registry key for use by subsequent processes during that same session. This doesn't use the existing registry key under HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Video that records the mode when CDS_UPDATEREGISTRY is used with ChangeDisplaySettingsEx() -- which explorer.exe does during start-up -- because a) that doesn't support the distinction between pixel size and point size for Retina modes, and b) in theory, apps could overwrite that. Signed-off-by: Ken Thomases <ken@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
-
Ken Thomases authored
winemac: Reorganize copy_display_modes() to clarify that the user's default mode is always included. Signed-off-by: Ken Thomases <ken@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
-
- 30 Jul, 2014 1 commit
-
-
Ken Thomases authored
-
- 10 Jan, 2014 1 commit
-
-
Ken Thomases authored
winemac: For ChangeDisplaySettingsEx(), if caller didn't specify, prefer non-interlaced and unstretched modes.
-
- 09 Jul, 2013 1 commit
-
-
Ken Thomases authored
-
- 28 Mar, 2013 1 commit
-
-
Ken Thomases authored
macdrv_ChangeDisplaySettingsEx() ignores the requested bpp, anyway, so we can report any values we think programs will want.
-
- 26 Mar, 2013 1 commit
-
-
Ken Thomases authored
-
- 18 Feb, 2013 3 commits
-
-
Ken Thomases authored
-
Ken Thomases authored
-
Ken Thomases authored
-
- 26 Dec, 2012 2 commits
-
-
Ken Thomases authored
-
Ken Thomases authored
-