- Jul 03, 2017
-
-
- Jul 02, 2017
-
-
- Jun 12, 2017
-
-
- Jun 09, 2017
-
-
Olivier Fourdan authored
Bug: 13607 If XPresentPixmap() fails, we would disable Present rather that waiting for a notification that will never arrive. But that relies on the actual window to be reported in the XError, which is not necessarily the case. Disable Xpresent for all screens as we are not sure we can tell which one from the resource id.
-
- Jun 02, 2017
-
-
Bug: 13613 Since commit 7115d1b4, we can't disable second (broken) vblank waiting code. glXSwapBuffers() already waits for v-blank (if enabled in driver), so any other "synthetic" waiting for v-blank can reduce performance (de-sync) without actual benefit. This patch removes old code to prevent waiting for vblank twice.
-
- Jun 01, 2017
-
-
Olivier Fourdan authored
Bug: 13608 Commit 58955779 (Use ximerama indices for _NET_WM_FULLSCREEN_MONITORS) introduced a regression because the monitor index was wrongly compared against the total number of monitors, which would falsely assume that the Xrandr query failed whereas it actually worked. Fix the false comparison and also use the screen size as fallback values in case the Xrandr really failed so that we don't end up using random uninitialized values.
-
- May 15, 2017
-
-
Olivier Fourdan authored
Prefer Present over GLX if both are available, and remove the environment variable "XFWM4_USE_PRESENT". Eventually, we'd rather use a command line option instead (TODO).
-
Olivier Fourdan authored
This is a leftover of the old (broken) vblank code.
-
Olivier Fourdan authored
Otherwise the current WM window might have vanished and we wouldn't know.
-
Olivier Fourdan authored
-
Olivier Fourdan authored
Bug: 9351 _NET_WM_FULLSCREEN_MONITORS uses Xinerama indices for multi-monitor fullscreen, but xfwm4 uses gdk indices which may differ. As a result, depending on the actual layout and which monitor is marked as primary, a fullscreen window could be placed on the wrong outputs. Fetch the Xinerama list and use the monitor size from there instead of relying on gdk monitor indices for _NET_WM_FULLSCREEN_MONITORS
-
Olivier Fourdan authored
Bug: 12534 This reverts commit 0dfb5540.
-
Olivier Fourdan authored
Bug: 13454 We would use the first monitor by default, but we'd rather use the primary monitor. Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
- Mar 21, 2017
-
-
Olivier Fourdan authored
NET_WM_STATE_FOCUS is set by the WM itself, it's not an unknown property.
-
-
- Mar 07, 2017
-
-
Olivier Fourdan authored
Bug: 13344 If a window is unmapped while the user is moving or resizing it, we would cancel the move but swallow the event, which would leave the window frame on screen as the main event handle would not get the unmap notify. Mark the client as gone when detected in the move/resize event loop, let the event get through to the main event handler that will free the client and shortcut the move/resize operation if the client is marked as gone.
-
- Mar 06, 2017
-
-
Olivier Fourdan authored
The panel is a dock window, and may appear differently as it is not focused by default by the window manager. Set the NET_WM_STATE_FOCUSED property on windows of type dock or spashscreen so that they don't get the state GTK_STATE_FLAG_BACKDROP set by default.
-
- Jan 19, 2017
-
-
Olivier Fourdan authored
Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
Olivier Fourdan authored
Bug: 13257 If for some reason XPresentPixmap() fails, we might end up waiting forever for a present complete notification that will never arrive. Check for possible errors after XPresentPixmap() and disable XPresent in case of error. Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
Olivier Fourdan authored
Add an API to retrieve the screen from the output window. Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
Olivier Fourdan authored
Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
Olivier Fourdan authored
Store the default display and add an API to retrieve it. Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
- Jun 15, 2016
-
-
Bug: 6427 Some mice have additional forward and backward buttons, use those with the easy-move key to cycle through the workspaces.
-
- Jun 13, 2016
-
-
Olivier Fourdan authored
Bug: 12634 xfwm4 would raise a client upon receiving the _NET_ACTIVE_WINDOW message but if the client provided an old timestamp, the window won't be focused (as the timestamp will be older than the last current X server time). To avoid this, only raise the window on focus event notification and when using click-to-focus mode. Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
- Jun 07, 2016
-
-
Olivier Fourdan authored
Bug: 12587 Relocating any window on the current monitor in multi-monitor setup when centered can cause issues with Citrix. Relocate only dialogs, and when not the exact same size as the screen. Signed-off-by:
Olivier Fourdan <fourdan@xfce.org>
-
- Jun 02, 2016
-
-
LibreOffice incorrectly sets its top level windows win_gravity field to StaticGravity. Resizing these windows to the left or upwards results in a corrupted application with the application window moved within the parent by the parent window resize. Metacity forces window gravity for all application windows to NorthWest, masking this application bug. xfwm4 should do the same. A bug has been filed against LibreOffice as well. Signed-off-by:
Keith Packard <keithp@keithp.com>
-