summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* bump version to 3.14.2, update NEWS3.14.2Alberts Muktupāvels2014-10-272-1/+7
|
* doap: update descriptionAlberts Muktupāvels2014-10-271-3/+3
|
* window: initialize few variablesAlberts Muktupāvels2014-10-251-0/+2
|
* configure.ac: update GTK required versionAlberts Muktupāvels2014-10-251-1/+1
| | | | | gtk_widget_set_margin_[start/end] are available starting with GTK 3.12.0 version.
* Fix some errors in manpagesDmitry Shachnev2014-10-152-3/+6
| | | | | | | * Escape hyphen signs properly. * Fix man -l -Tutf8 doc/man/metacity-message.1 >/dev/null reporting "warning [p 1, 1.5i]: cannot adjust line". * Update GTK2 to GTK3.
* configure.ac: Update major version number in messageDmitry Shachnev2014-10-151-2/+2
|
* bump version to 3.14.1, update NEWS3.14.1Alberts Muktupāvels2014-10-152-1/+10
|
* Updated Polish translationPiotr Drąg2014-10-121-109/+99
|
* window: initialize fullscreen to FALSEAlberts Muktupāvels2014-10-111-0/+1
| | | | | This fix random bug when applications without reason opens in fullscreen mode.
* Fix identification of CSD windows when checking whether to force fullscreenOwen W. Taylor2014-10-103-1/+20
| | | | | | | | | | | | | We try to exempt CSD windows from being forced fullscreen if they are undecorated and the size of the screen; however, we also catch almost all windows that *do* need to be forced fullscreen in this check, since they also have decorations turned off. Identify actual CSD windows by checking whether _GTK_FRAME_EXTENTS is set - GTK+ will always set this on CSD windows even if they have no invisible borders or shadows at the current time. https://bugzilla.gnome.org/show_bug.cgi?id=723029
* Updated Indonesian translationAndika Triwidada2014-10-101-94/+98
|
* Fix uninitialized variablesVincent Untz2014-10-091-0/+6
|
* bump version ro 3.14.0, update NEWS3.14.0Alberts Muktupāvels2014-10-092-1/+21
|
* remove wm-tester utilitiesAlberts Muktupāvels2014-10-098-1005/+1
|
* remove run-metacity.shAlberts Muktupāvels2014-10-092-119/+0
|
* remove MAINTAINERS fileAlberts Muktupāvels2014-10-092-44/+0
| | | | Maintainers are listed in metacity.doap file.
* Updated Hungarian translationGábor Kelemen2014-10-081-175/+235
|
* remove unused iconAlberts Muktupāvels2014-10-081-0/+0
|
* remove last use of custom iconsAlberts Muktupāvels2014-10-086-48/+31
|
* frames: Bump priority of style providersFlorian Müllner2014-10-081-1/+1
| | | | | | | | | Since GTK+ commit b1ad5c8abc2c, GtkSetting's CSS provider uses a priority of GTK_STYLE_PROVIDER_PRIORITY_SETTINGS, which means it will overwrite the ones we create ourselves. Bump the priority to fix dark window decorations. https://bugzilla.gnome.org/show_bug.cgi?id=688182
* frames: Explicitly initialize style contextsFlorian Müllner2014-10-081-0/+1
| | | | | | | | | We were relying on GTK+ emitting GtkWidget::style-updated during widget initialization to create the GtkStyleContexts used for window decorations. A recent GTK+ update broke this assumption, so do the necessary initialization ourselves. https://bugzilla.gnome.org/show_bug.cgi?id=671796
* fix a crash-on-exitDan Winship2014-10-081-2/+11
| | | | | | | | meta_frames_destroy() was not safe to be called multiple times, which was causing a crash on exit due to something else changing somewhere that makes it get called multiple times. https://bugzilla.gnome.org/show_bug.cgi?id=654489
* ui-frame: Add support for style variantsFlorian Müllner2014-10-082-1/+95
| | | | | | | | | | | | Rather than sharing a single style context between all frames, use a default style and one style per encountered variant. The value of the _GTK_THEME_VARIANT property should determine which style is attached to a particular frame, though for the time being the default style is used for every frame, as the window property cannot be accessed at the time the style is attached. This will be fixed in a later commit. https://bugzilla.gnome.org/show_bug.cgi?id=645355
* ui-frames: Delay attaching the style to new framesFlorian Müllner2014-10-082-2/+2
| | | | | | | | Like the setting of new frames' background is delayed until the frame is associated with its window, delay attaching the initial style, so that the correct style variant is picked. https://bugzilla.gnome.org/show_bug.cgi?id=645355
* core: Update frame style when _GTK_THEME_VARIANT changesFlorian Müllner2014-10-081-0/+3
| | | | | | | | | | | When the _GTK_THEME_VARIANT property changes, rather than just updating the window's theme_variant property, update its frame style as well, so that the window decoration reflects the requested variant. As the initial properties of a window may be read before its frame is created, there will be cases where the change is not picked up initially. https://bugzilla.gnome.org/show_bug.cgi?id=645355
* ui: Add meta_ui_update_frame_style()Florian Müllner2014-10-084-0/+27
| | | | | | | This method allows forcing a style update of a particular frame from the core, so that it can pick up style variants. https://bugzilla.gnome.org/show_bug.cgi?id=645355
* core: Allow retrieving the theme variant via core_get()Florian Müllner2014-10-082-0/+4
| | | | | | | To associate frames with the correct style variant, the UI will need access to the window's theme variant property. https://bugzilla.gnome.org/show_bug.cgi?id=645355
* window: Parse _GTK_THEME_VARIANT propertyFlorian Müllner2014-10-084-0/+33
| | | | | | | | | | | | Since version 3.0, GTK+ has support for style variants. At the moment, themes may provide a dark variant, which can be requested by applications via GtkSettings. The requested variant is exported to X11 via the _GTK_THEME_VARIANT property - support this property, in order to pick up the correct style variant in the future. https://bugzilla.gnome.org/show_bug.cgi?id=645355 NOTE: Patch is adapted for metacity.
* frame: Delay updating the background until the frame is readyFlorian Müllner2014-10-081-5/+5
| | | | | | | | | To determine the correct background style, the UI needs to access some frame properties via meta_core_get(); this call will bail out early if window->frame is unset, so delay the call until the association is made. https://bugzilla.gnome.org/show_bug.cgi?id=645355
* bump library version to 2:0:0Alberts Muktupāvels2014-10-071-1/+1
|
* add support for app-menu button in themeAlberts Muktupāvels2014-10-077-18/+76
| | | | | | | | | Add app-menu button support in themes. This is done only to support metacity theme format 3.5 version. Metacity will not show this button! Based on mutter commit: https://git.gnome.org/browse/mutter/commit/?id=c2ea650b3c484312c14f69b8b245ab117ef7c6e1
* remove option to attach modal dialogsAlberts Muktupāvels2014-10-062-17/+0
| | | | | This was added only to add support for metacity theme format version 3.2.
* don't show shadow for maximized windowsAlberts Muktupāvels2014-10-066-6/+83
|
* remove trailing whitespaceAlberts Muktupāvels2014-10-05103-3816/+3816
|
* add support for _GTK_FRAME_EXTENTSAlberts Muktupāvels2014-10-054-1/+84
| | | | Support for _GTK_FRAME_EXTENTS are based on mutter.
* window-props: improve properties handlingAlberts Muktupāvels2014-10-055-238/+313
| | | | All changes here are based on mutter.
* Fix property notifications for certain propertiesOwen W. Taylor2014-10-051-20/+20
| | | | | | | | | | | | | | If a property has a reload function, but the standard property-fetching mechanism isn't used (hooks->type == META_PROP_VALUE_INVALID), then the a logic error (introduced in January) caused the hook to never be run. This meant that changes to struts and icons weren't noticed. Same as: http://bugzilla.gnome.org/show_bug.cgi?id=572573 The fix here is different in detail from that applied to Metacity, but similar in spirit. http://bugzilla.gnome.org/show_bug.cgi?id=585980
* Revert "fix problem where the previous code ignored callbacks for properties ↵Alberts Muktupāvels2014-10-051-24/+47
| | | | | | | | | whose" This reverts commit 178b5ff626d747026fc9d03c7908c3f203fbd263. Conflicts: ChangeLog
* theme: replace MUTTER with METACITYAlberts Muktupāvels2014-10-041-1/+1
|
* resizepopup.c: don't use deprecated GtkMiscAlberts Muktupāvels2014-10-041-1/+5
|
* fixedtip.c: don't use deprecated GtkMiscAlberts Muktupāvels2014-10-041-1/+2
|
* tabpopup.c: don't use deprecated GtkMiscAlberts Muktupāvels2014-10-041-3/+1
|
* select-workspace.c: updateAlberts Muktupāvels2014-10-043-109/+108
|
* tabpopup.c: split out MetaSelectWorkspaceAlberts Muktupāvels2014-10-044-192/+254
|
* select-image.c: don't use deprecated GtkMiscAlberts Muktupāvels2014-10-043-116/+106
|
* tabpopup.c: split out MetaSelectImageAlberts Muktupāvels2014-10-044-114/+175
|
* tabpopup.c: don't use deprecated GtkAlignmentAlberts Muktupāvels2014-10-041-8/+2
|
* tabpopup.c: always show 5px outline borderAlberts Muktupāvels2014-10-041-25/+5
|
* tabpopup.c: don't show shadow for outline windowAlberts Muktupāvels2014-10-041-0/+5
| | | | Bug: https://bugzilla.gnome.org/show_bug.cgi?id=536573
* compositor-xrender: don't add shadows to ARGB windowsAlberts Muktupāvels2014-10-041-0/+7
|
View Lorry Controller Status