- 25 Apr, 2017 22 commits
-
-
Alexandre Julliard authored
Signed-off-by:Alexandre Julliard <julliard@winehq.org>
-
Alexandre Julliard authored
Signed-off-by: -
Akihiro Sagawa authored
Signed-off-by:
Akihiro Sagawa <sagawa.aki@gmail.com> Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
Michael Stefaniuc <mstefani@winehq.org> Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
Hans Leidekker <hans@codeweavers.com> Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <z.figura12@gmail.com> Signed-off-by:
-
Huw Davies authored
Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Austin English authored
Signed-off-by:
Austin English <austinenglish@gmail.com> Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Ken Thomases authored
If either of the recursive calls would have the same x2, y2, x3, and y3 arguments as the current call, the path is as flat as the precision of floats allows. Signed-off-by:
Ken Thomases <ken@codeweavers.com> Signed-off-by:
Vincent Povirk <vincent@codeweavers.com> Signed-off-by:
-
Henri Verbeet authored
Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Henri Verbeet authored
Signed-off-by:
-
Henri Verbeet authored
Signed-off-by:
-
- 24 Apr, 2017 18 commits
-
-
Ken Thomases authored
It doesn't seem to work well. In full-screen mode, newly-added windows don't always properly resize to fill the screen, so they're not the same size as the windows they're nominally tabbed with. In non-full-screen mode, switching between tabs sometimes causes the windows to grow in height each time. Etc. Signed-off-by:
-
Ken Thomases authored
They shouldn't get a separate space; they should stick with their parent (owner). Signed-off-by:
-
Ken Thomases authored
Simply ordering them out leaves the user on the full-screen space, which is now an empty black screen. Closing the window closes the space, too. Signed-off-by:
-
Ken Thomases authored
winemac: Defer ordering a window out if it's in the process of entering or exiting Cocoa full-screen mode. Cocoa doesn't handle the window being ordered out or closed during the animation well and leaves a ghost window around. Signed-off-by:
-
Ken Thomases authored
The code had been handling ordering sibling windows relative to each other, including windows neither of which were child windows. However, it wasn't properly handling other relationships (e.g. cousins, nieces, uncles, etc.). The reason this is complicated is that Cocoa keeps child windows in a fixed relative order to their parent and siblings. The normal -orderWindow:relativeTo: method doesn't work. One has to remove the children from the parent and re-add them in the desired order. Signed-off-by:
-
Ken Thomases authored
Signed-off-by:
-
Ken Thomases authored
Cocoa does this automatically for non-owned windows and informs the back end via a different mechanism (WINDOW_BROUGHT_FORWARD). However, for owned windows (child windows in Cocoa parlance), Cocoa does not change their z-order relative to the owner (parent) or sibling owned windows when clicked. So, we have to move the window in user32's z-order so that it gets moved appropriately on screen in response. Signed-off-by:
-
Ken Thomases authored
winemac: Add a category on NSEvent to simplify checking if the Command key (and only that modifier) is pressed for an event. Signed-off-by:
-
Ken Thomases authored
winemac: Move the window to the front of the z-order in SetFocus if it's the foreground window and not already in the front. Ideally, user32 would adjust its z-order for window activation as happens on Windows. Then, the Mac driver would just reflect such changes in the Cocoa windows. But user32 doesn't do that. SetActiveWindow() and SetForegroundWindow() just adjust focus and status. This is an attempt to achieve a similar result. Signed-off-by:
-
Ken Thomases authored
winemac: Sync the frame of the Cocoa view for a window's client area while handling a frame-changed event. Fixes a problem where the client area view would not be resized as the user resizes the Cocoa window. Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Hugh McMaster authored
Signed-off-by:
Hugh McMaster <hugh.mcmaster@outlook.com> Signed-off-by:
-
Hugh McMaster authored
Signed-off-by:
-
Sebastian Lackner authored
Signed-off-by:
Sebastian Lackner <sebastian@fds-team.de> Signed-off-by:
-
Michael Müller authored
Signed-off-by:
Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Signed-off-by:
-
Alistair Leslie-Hughes authored
Signed-off-by:
-
Sebastian Lackner authored
Signed-off-by:
-
Michael Müller authored
Signed-off-by:
Michael Müller <michael@fds-team.de> Signed-off-by:
-
