| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
They don't need double buffer combination since they have no
client-side children, and creating pixmaps for them is risky
since they could disappear at any time.
May fix bug 598476 and 603652.
|
|
|
|
| |
This fixes problems in clutter-gtk. See bug 603619.
|
|
|
|
| |
(cherry picked from commit 22d1d0d5077a518c1e1a3622678cb7d1e6ab8e87)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It may happen when turning a client side window into a native window
that the window, or some of its children with the same native parent
have extension events enabled, and thus have an input window enabled
for the native parent which needs to change as the window is made
native.
We fix this by temporarily disabling extension events on all the affected
windows while we create the native window, and then reenable them afterwards.
This fixes: https://bugzilla.redhat.com/show_bug.cgi?id=544624
(cherry picked from commit 159214173d2ec626dd0390a5fd0e5beaa6404f6e)
|
|
|
|
|
|
|
|
|
|
|
|
| |
All kinds of lines (lines, segments, arcs, etc) need to take into
account the line properties (width, miter limit, joins, caps, etc)
to get proper damage extents.
This is not really possible to do, but we can make it likely to work
with some ad-hoc estimates.
Fixes bug 603904.
(cherry picked from commit 98a9c5c69a796b48d3797a35a301dabe1dcb2430)
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fix in 786b589d95077b465dcc2311ff2489ee7bb9a49f for the
"Cannot click buttons more than once without moving the mouse cursor"
did not correctly handle setups with multiple screens in one display.
We need to handle the case where the first XQueryPointer returns
a different root window than the default one.
This fixes bug 597386 (agaion)
(cherry picked from commit 48fc0f36c28fb0317a3433bafbe7bf8ae8a01171)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't really need to filter these out, it was just a leftover
safety check to not override the GDK_POINTER_MOTION_MASK.
Furthermore when we changed behaviour to not always select for native
pointer motion it is actually wrong. We'll still get normal motion
events for the toplevel which we will emulate as button motion on the
child, but the button motion mask will not be inherited by implicit
grabs which makes us not get any motion events during grabs.
This fixes bug 601473
(cherry picked from commit b509f28559dba03684ecc88acac498b6f27d2ebf)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=591438
(cherry picked from commit ee2c797e700ec933fafce48b405dda53fdb228da)
|
|
|
|
|
|
| |
This looks nicer, and allows us to make the url-hook work again
for the website url. Fixes bug 603201.
(cherry picked from commit 478ca88ae5393c422f7c72795d7dd0df29108511)
|
|
|
|
|
|
| |
This broke when we started allowing Super, Hyper and Meta as
accel modifiers. See bug 601959.
(cherry picked from commit c08ed56f13bafff56fe3a827baf78bb0d2a1f872)
|
|
|
|
|
|
| |
Check that the child of a popup menu item is actually a GtkAccelLabel
before setting its "accel-closure" property.
(cherry picked from commit 25a8c7316d4acb2fe3ada0bef3c087875bc95e45)
|
|
|
|
|
|
| |
This was committed to fix bug 568263, but it is not correct, as
pointed out in 601611.
(cherry picked from commit 6dfb21e616bdf1e1db7ed86bff08fcb68210f17e)
|
|
|
|
|
|
|
| |
Although it isnt' allowed by the XEMBED protocol, its possible
that the plug window will be reparented out of the socket without
the socket having done so. See bug 123569. Patch by David Jander.
(cherry picked from commit 84254039f261b4c4421246ed4b90127711858af5)
|
|
|
|
|
|
| |
We came up short when the image width is not a multiple of 8.
Bug 585383, fix by Felix Riemann.
(cherry picked from commit 869ee7f232d2afcf2c08003e4f279e21b58b9581)
|
|
|
|
|
| |
By moving the g_return_if_fail() checks into individual monitor functions.
See bug 561130.
|
|
|
|
|
| |
There's no reason to do our expensive round-trips for an override-redirect
window; just use local information. See bug 581145. Patch by Owen Taylor.
|
|
|
|
|
| |
Bug #602724.
(cherry picked from commit 7abd4d1359ec6b376601169198bbe9a025461df3)
|
|
|
|
|
| |
Invisible text has been working reasonably well since 2.8.
(cherry picked from commit b72c2143b0608f0f5fb32abb9053e7bcd0541de7)
|
|
|
|
|
| |
We were not paying attention to consumed modifiers when adding
virtual modifiers. This fixes RH bug 537567.
|
|
|
|
|
| |
Bug #602725.
(cherry picked from commit ba218a77892739a3668a3369370afb5d41de8c03)
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=590800
(cherry picked from commit 04d7d8105629532875d2bf1c3a454184fd6d1b40)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you add a new ui node that was recently removed it will still be
in the tree, but marked dirty. In this case we previously just used
the old node, which meant it wouldn't get the same position as if
the dirty nodes had been processed first (and deleted) before the
new node was added.
We handle this by detecting this case and reposition the node as if
it was new.
https://bugzilla.gnome.org/show_bug.cgi?id=603128
(cherry picked from commit 7b19640d8f579da5d802d2a6f72128a6f29a5f33)
|
| |
|
| |
|
|
|
|
|
| |
This modifies the previous commit to be according the upstream libjpeg
maintainers recommendations. See bug 588740.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The previous implementation was modifying the passed in window ("private") rather than deriving information from it. Also the type hints are now forwarded like in the X11 implementation instead of ignored.
The effect of the unfinished client-side-window porting was e.g. a crash with Dia's navigation window which happened to create a window with an apparent depth of zero.
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=599446
|
|
|
|
|
| |
The assumption that scale_num will be automatically be 1 is no longer
with libjpeg7. So set it explicitly. Bug #588740.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we just invalidate some area from the app we don't need to clear
windows with no exposure mask, because that wouldn't have happened pre-csw
anyway. Additionally we can avoid such clearing for native windows in cases
where the xserver already did the clearing like on exposes or when resizing
toplevels.
This means we don't fully redraw a GtkSocket when it resizes, thus
avoiding flicker in gnome-mplayer as reported in this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=598050
(cherry picked from commit 9e51c10edc50333997a28c221b200cc6f83bdcef)
|
|
|
|
| |
(cherry picked from commit 9ae0d9a44f785564a9b100a58b34a9dcabf61724)
|
|
|
|
|
|
|
|
| |
Backends that support native window background setting (and that clears
new window areas to this color/pixmap) should set this to true.
Currently only X11 supports this.
(cherry picked from commit 39993f147f05a3711b415635c592200f28db5dcd)
|
|
|
|
|
|
|
| |
When moving or scrolling a window with native children, there is no
need to expose the areas that are copied by the windowing system
as part of moving/resizing the native windows anyway.
(cherry picked from commit 4cd5c9894268966d4d8a2586a7d5a7c5c440ee33)
|
|
|
|
|
| |
Exposing when you hide a hidden window is just a waste of time.
(cherry picked from commit a299797883440e7671956d73761885ec102840b0)
|
|
|
|
|
|
| |
Clearing will directly modify the contents of the window, so we need
to flush any outstanding moves or double-buffering.
(cherry picked from commit 8c1ea38d84468a9098e88573ba714cbbe3c80ed5)
|
|
|
|
| |
Fixes bug #381371.
|
| |
|
| |
|
|
|
|
|
| |
Don't recreate the settings color hash every time, repopulate it
instead. This avoids invalidating the references held by RcContexts.
|
|
|
|
|
| |
Several fixes by Ray Strode and Peter Hutterer to make compose-parse.py
work with the current X.org Compose file.
|
|
|
|
|
| |
This patch includes additions to the X.org Compose file from the
last year. Patch by Peter Hutterer
|