summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* display: Unset grab_frame_action in meta_display_end_grab_opwip/message-trayDebarshi Ray2012-07-181-0/+2
| | | | | | | | | | | Otherwise, if the user had moved the windows around using a mouse, they can not be moved beyond the top edge of the primary monitor when the tray needs to be brought up, . This is because constrain_titlebar_visible looks at grab_frame_action and thinks that the movement is being caused by the user trying to move the windows up by grabbing the frame. Fixes: https://bugzilla.gnome.org/677215
* Updated Traditional Chinese translation(Hong Kong and Taiwan)Chao-Hsiung Liao2012-07-172-320/+323
|
* Bump version to 3.5.43.5.4Florian Müllner2012-07-162-1/+24
| | | | Update NEWS
* window: Do not restore tiling on unmaximizeFlorian Müllner2012-07-161-9/+0
| | | | | | | | When we consider tiling a special case of maximization, it makes more sense to always unmaximize to the normal state rather than restoring a previous tile state. https://bugzilla.gnome.org/show_bug.cgi?id=677565
* window: Handle changes of the attach-modal-dialogs preferenceFlorian Müllner2012-07-161-6/+12
| | | | | | | | | | Currently we decide whether a modal dialog should be attached or not when mapping it, i.e. we don't pick up preference changes that happen while the dialog is up. It's not really a big deal given that modal dialogs are usually transitory, but it's easy enough to add a bit of extra polish ... https://bugzilla.gnome.org/show_bug.cgi?id=679904
* workspace: Respect the not_this_one parameter passed inJasper St. Pierre2012-07-161-1/+1
| | | | | | | In the case of focus-follows-mouse, we need to ensure that we do not select a certain window after closing another one. https://bugzilla.gnome.org/show_bug.cgi?id=675982
* Updated Spanish translationDaniel Mustieles2012-07-161-19/+20
|
* Assamese translation updatedNilamdyuti Goswami2012-07-161-12/+13
|
* Updated Belarusian translation.Ihar Hrachyshka2012-07-151-161/+166
|
* Reduce amount of markup in translated messagesMatthias Clasen2012-07-141-2/+6
| | | | | | | Markup in messages is fragile and tends to break in translations. This patch reduces the amount of markup as far as possible. https://bugzilla.gnome.org/show_bug.cgi?id=679660
* constraints: Remove unused variableDebarshi Ray2012-07-141-2/+0
|
* shadow-factory: Don't use a top-fade on attached modalsFlorian Müllner2012-07-141-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=674499
* constraints: Center modal dialogs on their parentFlorian Müllner2012-07-142-11/+7
| | | | | | ... rather than attaching them to the parent's title bar. https://bugzilla.gnome.org/show_bug.cgi?id=674499
* Assamese translation reviewedNilamdyuti Goswami2012-07-131-302/+289
|
* keybindings: Use G_DEFINE_BOXED_TYPEJasper St. Pierre2012-07-131-12/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=673824
* Updated Hebrew translation.Yaron Shahrabani2012-07-101-147/+149
|
* Updated Norwegian bokmål translationKjartan Maraas2012-07-101-157/+104
|
* constraints: fix mem leak in meta_window_constrain()Pavel Vasin2012-07-081-3/+10
| | | | | | | MetaFrameBorders leaked when orig_borders != NULL and window->fullscreen == TRUE https://bugzilla.gnome.org/show_bug.cgi?id=679153
* *BSD build fix: Include sys/wait.h as described in POSIX specsJasper Lievisse Adriaanse2012-07-081-1/+1
|
* Updated Bulgarian translationAlexander Shopov2012-07-041-156/+100
|
* window: Also use hide-titlebar-when-maximized when tiledFlorian Müllner2012-07-031-1/+2
| | | | | | | | Side-by-side tiling is conceptually very close to maximization ("half-maximized"), so it makes sense to also hide the titlebar in this state if requested by the application. https://bugzilla.gnome.org/show_bug.cgi?id=679290
* prefs: add get_/set_ignore_request_hide_titlebar ()Rico Tzschichholz2012-07-013-1/+17
| | | | | | | | Enables the possibility to ignore GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED to prevent hiding the titlebar of applications even if they requested so. https://bugzilla.gnome.org/show_bug.cgi?id=678947
* Make it possible to reimplement move-to-workspace keybindings from pluginsGiovanni Campagna2012-06-255-1/+23
| | | | | | | Export the necessary functions so that a plugin that wishes to do so can reimplement those keybindings without loss of functionality. https://bugzilla.gnome.org/show_bug.cgi?id=674104
* Make meta_workspace_get_neighbor() publicGiovanni Campagna2012-06-253-3/+15
| | | | | | | There is no need for this function to be private, and it can greatly simplify gnome-shell code handling workspace switch. https://bugzilla.gnome.org/show_bug.cgi?id=674104
* Bump version to 3.5.33.5.3Florian Müllner2012-06-252-1/+20
| | | | Update NEWS
* meta-window-actor: Fix a potential crash in the window shaping codeJasper St. Pierre2012-06-251-7/+8
| | | | | | | | | There was a potential case where we were trying to use uninitialized memory, in the case where the X server threw an error during XShapeGetRectangles. In this case, we need to use the implicit shape for the window, which means we need to rearrange code flow to make it work. https://bugzilla.gnome.org/show_bug.cgi?id=677977
* meta-plugin-manager: Guard against a NULL start vfuncJasper St. Pierre2012-06-251-1/+6
| | | | | | The default plugin has no such vfunc. https://bugzilla.gnome.org/show_bug.cgi?id=678238
* mutter: Use the default plugin by defaultJasper St. Pierre2012-06-251-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=678238
* window: Make some window methods publicJasper St. Pierre2012-06-252-22/+22
| | | | | | | There's no reason they aren't, right now. Extensions should be able to use these. https://bugzilla.gnome.org/show_bug.cgi?id=678126
* Updated Galician translationsFran Diéguez2012-06-251-159/+146
|
* prefs: remove some obsolete header definitionsRico Tzschichholz2012-06-181-6/+0
|
* Updated French translationBruno Brouard2012-06-151-111/+99
|
* Updated Arabic translationKhaled Hosny2012-06-131-120/+108
|
* Fix bad declarationsJasper St. Pierre2012-06-112-2/+2
| | | | meta_screen_get_current_monitor now returns an integer, not a pointer.
* core: Fix meta_screen_get_current_monitorMarc-Antoine Perennou2012-06-111-1/+1
| | | | | | | | | fixes 45952093463e5d354e4f0d7c4ded6ab0d601d959 We're supposed to return an index from here now, no longer a pointer to the current monitor. Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
* frames: Add a multiplier to increase the size of resize cornersJasper St. Pierre2012-06-081-8/+9
| | | | | | Now the resize corners will extend into the actual border edges. https://bugzilla.gnome.org/show_bug.cgi?id=677669
* screen: Add new public meta_screen_get_current_monitor APITim L2012-06-085-8/+25
| | | | | | | | Similar to meta_screen_get_primary_monitor, this returns a monitor index. The monitor that the pointer is on. The previous private implementation has been renamed to meta_screen_get_current_monitor_info. https://bugzilla.gnome.org/show_bug.cgi?id=642591
* main: Support -r as the equivalent of --replaceJasper St. Pierre2012-06-081-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=676857
* meta-window-actor: Don't unredirect shaped windowsJasper St. Pierre2012-06-081-0/+3
| | | | | | | | | | If a window has its BoundingRegion shaped, we shouldn't unredirect it, as it expects the rest of the windows from being shown under it. This prevents applications like the Skype screen recorder or gtkRecordMyDesktop which want to show a "border" around the recorded area from being unredirected, giving the appearance of making the desktop freeze. https://bugzilla.gnome.org/show_bug.cgi?id=677657
* meta-window-actor: Refactor should_unredirect a bit moreJasper St. Pierre2012-06-081-23/+25
| | | | | | "Flat is better than nested" https://bugzilla.gnome.org/show_bug.cgi?id=677657
* Updated Slovenian translationMatej Urbančič2012-06-081-247/+125
|
* Updated Spanish translationDaniel Mustieles2012-06-061-27/+28
|
* meta-plugin-manager: Only allow one plugin to be loadedJasper St. Pierre2012-06-057-300/+113
| | | | | | | | | | | The "multiple plugins loaded at once" strategy was always a big fiction: while it may be viable if you're super careful, it's fragile and requires a bit of infrastructure that we would be better off without. Note that for simplicity, we're keeping the MetaPluginManager, but it only manages one plugin. A possible future cleanup would be to remove it entirely. https://bugzilla.gnome.org/show_bug.cgi?id=676855
* meta-plugin: Remove "disabled" featureJasper St. Pierre2012-06-053-97/+61
| | | | | | It's just code cruft that nobody's using https://bugzilla.gnome.org/show_bug.cgi?id=676855
* meta-plugin: Kill off "features"Jasper St. Pierre2012-06-053-82/+13
| | | | | | | | We already check that the plugin has the appropriate vfunc in the klass structure, so we shouldn't need to check for the same data again with a "features" long. https://bugzilla.gnome.org/show_bug.cgi?id=676855
* mutter: Only allow one plugin to be loadedJasper St. Pierre2012-06-051-15/+7
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=676855
* meta-plugin: Remove some cruftJasper St. Pierre2012-06-051-16/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=676855
* main: Don't call g_type_init from meta_initJasper St. Pierre2012-06-052-2/+2
| | | | | | For the plugin system, GType has to have been initialized by now. https://bugzilla.gnome.org/show_bug.cgi?id=676855
* util: Don't generate a backtrace on every G_LOGJasper St. Pierre2012-06-055-40/+0
| | | | | | | | We may not show the backtrace, but it's prohibitly expensive to generate, so don't. If someone wants a backtrace they can use the appropriate G_DEBUG environment variable plus GDB. https://bugzilla.gnome.org/show_bug.cgi?id=676855
* Bump version to 3.5.23.5.2Florian Müllner2012-06-052-2/+24
| | | | Update NEWS
View Lorry Controller Status