summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* frames: use correct variable in for loop assignmentgnome-3-18Shantanu Goel2017-04-041-1/+1
| | | | | | | | | | | | | | | | | | | update_context_styles is using the wrong variable when advancing to the next key in the hash table which can cause an infinite loop if # of variants is ever greater than 1. This problem was originally reported here: https://github.com/linuxmint/Cinnamon/issues/5254 The following patch was commited in Mint: https://github.com/linuxmint/muffin/commit/6120bdde This patch is just a shorter version of the Mint patch and they deserve all the credit for the idea. https://bugzilla.gnome.org/show_bug.cgi?id=780254
* window: send synthetic ConfigureNotify eventsAlberts Muktupāvels2017-03-231-25/+89
| | | | | | | | We might receive ConfigureRequest to change only window stacking order. According to ICCCM section 4.1.5 we should send synthetic ConfigureNotify event. https://bugzilla.gnome.org/show_bug.cgi?id=582580
* Revert "window: send synthetic ConfigureNotify events"Alberts Muktupāvels2017-03-232-85/+64
| | | | This reverts commit 15940e701cef107666df63c7318367c564e5f37e.
* window: send synthetic ConfigureNotify eventsAlberts Muktupāvels2017-03-212-64/+85
| | | | | | | | We might receive ConfigureRequest to change only window stacking order. According to ICCCM section 4.1.5 we should send synthetic ConfigureNotify event. https://bugzilla.gnome.org/show_bug.cgi?id=582580
* theme: fix gradients with one alpha valueAlberts Muktupāvels2017-02-251-4/+13
| | | | | | Commit 71d5decc42f3367bcbe2c4656356edd0f94d9feb ported gradient code from GdkPixbuf to cairo. Ported code wrongly assumed that alpha values always match color stops.
* compositor: set cw->window to NULL in xrender_free_windowAlberts Muktupāvels2016-10-251-0/+1
|
* compositor: don't remove window on UnmapNotify eventAlberts Muktupāvels2016-09-261-1/+16
| | | | | | | Compositor still needs to know about unmapped windows to properly handle window stacking order. https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050
* NEWS: fix bug numberAlberts Muktupāvels2016-08-221-1/+1
|
* bump version to 3.18.7, update NEWS3.18.7Alberts Muktupāvels2016-08-122-1/+6
|
* frames: use cairo_push_group in meta_frames_get_maskAlberts Muktupāvels2016-08-101-0/+5
|
* compositor: fix memory leakAlberts Muktupāvels2016-07-141-3/+12
|
* bump version to 3.18.6, update NEWS3.18.6Alberts Muktupāvels2016-07-122-1/+7
|
* don't show the resize popup for 2 x 2 size incrementsGiovanni Campagna2016-07-071-2/+2
| | | | | | | | | | | | | In a HiDPI environment, all gtk+ apps will report a 2 x 2 size increment to avoid odd size. But that does not mean they are resizing in cells like terminals, so they resize popup should not be shown. Ideally, we should ignore <= scale x scale increments, but in practice scale is 1 or 2, and even in a lo-dpi setting a 2 x 2 increment makes little sense so let's keep the patch simple. https://bugzilla.gnome.org/show_bug.cgi?id=746420
* theme: fix gradientsAlberts Muktupāvels2016-07-071-3/+9
|
* theme: fix 'use cairo to render gradient' commitAlberts Muktupāvels2016-07-071-2/+2
|
* theme: use cairo to render gradientAlberts Muktupāvels2016-07-071-20/+82
|
* constraints: validate fullscreen monitors before using themAlberts Muktupāvels2016-06-291-1/+22
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=766156
* frames: restore window resize using titlebarAlberts Muktupāvels2016-06-271-1/+1
| | | | https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1596574
* bump version to 3.18.5, update NEWS3.18.5Alberts Muktupāvels2016-06-252-1/+13
|
* frames: remove clip_to_screen optimizationAlberts Muktupāvels2016-06-241-34/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=538438
* window: fix meta_window_get_titlebar_rectAlberts Muktupāvels2016-06-222-8/+12
| | | | | | | | | | | | At least two places before 90b36abebdf69be0abaec4015d01e46296f6f5d6 commit used screen coordinates. Update meta_window_get_titlebar_rect function to return titlebar rectange in screen coordinates. This also reverts first change in place.c that did not make any sense. x and y in titlebar_rect always was 0 meaning that we always used CASCADE_FUZZ value while previously visible border size was used. https://bugs.launchpad.net/ubuntu/+source/metacity/+bugs/1509031
* compositor: don't try to paint window that is not viewableAlberts Muktupāvels2016-06-181-0/+3
| | | | https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1592953
* compositor: use only one error traps in free_winAlberts Muktupāvels2016-05-301-10/+9
| | | | | | free_win function already has two error traps, but there is other functions that could generate X errors. Replace existing traps with one that is added for whole function.
* compositor: add error trap in free_winAlberts Muktupāvels2016-05-251-0/+3
| | | | | | | | | | It seems that picture might be destroyed with window if it is created by passing window id as drawable to XRenderCreatePicture. Add error trap around XRenderFreePicture to avoid Metacity crash with RenderBadPicture error. https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687
* frames: ignore event outside of frame in get_controlAlberts Muktupāvels2016-05-241-0/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=436416
* iconcache: don't crash on a non-alpha mask pixmapOwen W. Taylor2016-05-231-4/+5
| | | | | | | We assume when applying a mask that it is a depth-1 pixmap that cairo interprets as alpha. So ignore a non-depth-1 mask. https://bugzilla.gnome.org/show_bug.cgi?id=641975
* iconcache: Correctly interpret monochrome iconsOwen W. Taylor2016-05-231-2/+42
| | | | | | | | Getting the contents of a depth-1 pixmap through cairo gives us an alpha pixmap. We need to convert to a monochrome pixmap as is expected by the ICCCM definition of WM_HINTS. https://bugzilla.gnome.org/show_bug.cgi?id=641975
* iconcache: Fix apply_maskJasper St. Pierre2016-05-231-8/+2
| | | | | | | | apply_mask made some wrong assumptions that became untrue after rendering_cleanup landed, such as the number of channels in the pixmap, causing corruption. https://bugzilla.gnome.org/show_bug.cgi?id=641975
* bump version to 3.18.4, update NEWS3.18.4Alberts Muktupāvels2016-04-242-1/+7
|
* compositor: don't destroy client_region on unmapAlberts Muktupāvels2016-04-171-1/+7
|
* compositor: don't crash when xregion is NoneAlberts Muktupāvels2016-04-171-0/+3
|
* core: hide new symbolsAlberts Muktupāvels2016-04-172-0/+2
|
* frames: use CAIRO_CONTENT_COLOR for cache surfaceAlberts Muktupāvels2016-04-161-1/+1
|
* frame: always use the client window's visualAlberts Muktupāvels2016-04-161-42/+4
|
* frames: revert "clip drawing to visible region for metacity themes"Alberts Muktupāvels2016-04-161-19/+1
|
* theme: clip metacity theme drawing to rounded cornersAlberts Muktupāvels2016-04-161-0/+78
|
* compositor: use window mask in paint_windowsAlberts Muktupāvels2016-04-161-15/+69
|
* compositor: redo xrender_get_window_surfaceAlberts Muktupāvels2016-04-161-8/+140
|
* compositor: keep more info when window is shadedAlberts Muktupāvels2016-04-161-31/+133
|
* compositor: create picture with window maskAlberts Muktupāvels2016-04-162-127/+130
|
* compositor: rename window_size to visible_regionAlberts Muktupāvels2016-04-151-40/+52
|
* compositor: add client_regionAlberts Muktupāvels2016-04-151-0/+73
|
* compositor: rename border_size to window_regionAlberts Muktupāvels2016-04-151-25/+34
|
* compositor: use correct xid when removing windowAlberts Muktupāvels2016-04-151-1/+7
|
* window: clear the frame borders before calculating the unfullscreen rectJasper St. Pierre2016-04-151-0/+2
| | | | | | Going from fullscreen to unfullscreen involves a frame border size, so in order to properly interpret the saved rect size, we need to make sure that the frame borders are fully up to date.
* window: use the correct frame size during unmaximizeAlberts Muktupāvels2016-04-151-0/+6
| | | | | | | | | | When unmaximizing, we changed bits of window state, then called out to code that used the frame extents *before* we cleared old cached extents. Clear the cache up-front as soon as we change the window state. Based on mutter commit: https://git.gnome.org/browse/mutter/commit/?id=8d5ab6b5b34a3dbeaba6033c31d06090579ed574
* compositor: add window back to compositorAlberts Muktupāvels2016-04-132-20/+18
| | | | | | | | | Remove window from compositor when calling meta_window_free and make sure to re-add window to the compositor when we re-create MetaWindow on MapRequest. https://bugzilla.gnome.org/show_bug.cgi?id=504876 https://bugzilla.gnome.org/show_bug.cgi?id=751833
* frame: cache bordersOwen W. Taylor2016-04-136-5/+57
| | | | | | | | | | | | Cache the computed border size so we can fetch the border size at any time without worrying that we'll be spending too much time in the theme code (in some cases we might allocate a PangoFontDescription or do other significant work.) The main effort here is clearing the cache when various bits of window state change that could potentially affect the computed borders. https://bugzilla.gnome.org/show_bug.cgi?id=707194
* frame: expose meta_frame_get_maskAlberts Muktupāvels2016-04-122-8/+4
|
* theme (gtk+): stop hiding titlebar buttons in dialogsFlorian Müllner2016-04-111-2/+0
| | | | | | | As design patterns have evolved, dialogs that use CSD do use titlebar buttons, so it's time to re-enable them for SSD as well. https://bugzilla.gnome.org/show_bug.cgi?id=641630
View Lorry Controller Status