- 14 May, 2016 31 commits
-
-
Andrey Gusev authored
Signed-off-by:
Andrey Gusev <andrey.goosev@gmail.com> Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Ken Thomases authored
winemac: When a child window's client area is equal to its whole area, use a single Cocoa view for both. This should be a common case and will reduce the number of Cocoa views. Signed-off-by:
Ken Thomases <ken@codeweavers.com> Signed-off-by:
-
Ken Thomases authored
This only really affects OpenGL child windows. GDI rendering to the window surface is still only blitted to the window's content view. The descendant views don't draw and so are transparent, letting the content view show through. Using Cocoa views for child windows fixes a problem where changes to the position and visibility of child GL windows didn't properly affect the Cocoa GL view. Hiding, showing, and moving the top-level window affected the Cocoa window and thus, indirectly, the GL view. Moving the child GL window itself was propagated to the GL view, so that worked. But hiding, showing, or moving any of the intervening ancestors of the child GL window didn't properly affect the GL view. Neither did hiding or showing the child GL window itself. This also slightly improves the clipping of the GL view by its ancestors, although it still doesn't work quite right due to Cocoa bugs. There are also remaining bugs with z-order among multiple GL views and clipping by overlapping siblings. I hope to eventually fix those using Core Animation layers, for which this is a prerequisite. Signed-off-by:
-
Ken Thomases authored
Signed-off-by:
-
Ken Thomases authored
Minor no-op refactoring that makes subsequent commits cleaner. Signed-off-by:
-
Ken Thomases authored
Callers can use macdrv_set_view_superview() to do that separately. Signed-off-by:
-
Ken Thomases authored
Signed-off-by:
-
Ken Thomases authored
Remove the no-longer-used functionality of potentially moving the view from one window to another. That has been taken over by macdrv_set_view_superview(). Signed-off-by:
-
Ken Thomases authored
This allows for nesting views in a hierarchy rather than only ever adding them as direct subviews of the window content view. This functionality will be used in subsequent commits. This takes over some of the functionality of macdrv_set_view_window_and_frame(), which will be removed in a subsequent commit. Signed-off-by:
-
Ken Thomases authored
winemac: Remove the assumption that OpenGL views are always immediate subviews of the window content view. Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Andrew Eikum authored
Signed-off-by:
Andrew Eikum <aeikum@codeweavers.com> Signed-off-by:
-
Maarten Lankhorst authored
Signed-off-by:
-
Maarten Lankhorst authored
Signed-off-by:
-
Maarten Lankhorst authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
Piotr Caban <piotr@codeweavers.com> Signed-off-by:
-
Piotr Caban authored
msvcp110: Use locale_string::assign instead of freeing and allocating new object in _Locinfo__W_Getdays. Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Kirill K. Smirnov authored
Signed-off-by:
Kirill K. Smirnov <kirill.k.smirnov@gmail.com> Signed-off-by:
-
Akihiro Sagawa authored
Signed-off-by:
Akihiro Sagawa <sagawa.aki@gmail.com> Signed-off-by:
-
Kim Malmo authored
Signed-off-by:
Kim Malmo <berencamlost@msn.com> Signed-off-by:
-
Julian Rüger authored
Signed-off-by:
Julian Rüger <jr98@gmx.net> Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
Michael Stefaniuc <mstefani@redhat.de> Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Andrey Gusev authored
Signed-off-by:
-
Kirill Smirnov authored
Signed-off-by:
Hans Leidekker <hans@codeweavers.com> Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
Alex Henrie <alexhenrie24@gmail.com> Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Gerald Pfeifer authored
Signed-off-by:
Gerald Pfeifer <gerald@pfeifer.com> Signed-off-by:
-
- 06 May, 2016 9 commits
-
-
Jacek Caban authored
Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
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: -
Andrey Gusev authored
Signed-off-by:
-
Kim Malmo authored
Signed-off-by:
-
