summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Update Arabic translationKhaled Hosny2013-10-071-347/+301
|
* MetaIdleMonitor: protect the monitor instance while calling destroy notifyGiovanni Campagna2013-09-261-0/+2
| | | | | | | | | | | | | The destroy notify for a DBus watch holds a reference to the IdleMonitor, but the IdleMonitorWatch object doesn't (it knows all watches will be destroyed before the monitor is, so it doesn't need one). This means that the DBus watch reference can be the only one keeping the IdleMonitor alive (expecially true for device idle monitors, which are only used by g-s-d/cursor), and that means that calling the destroy notify freezes the monitor (and the next X calls access garbage). https://bugzilla.gnome.org/show_bug.cgi?id=708420
* constraints: don't apply fullscreen workarounds for CSD windowsGiovanni Campagna2013-09-261-3/+5
| | | | | | | | If you maximize a CSD window on a monitor without struts, it ends up taking the whole monitor size, but it doesn't mean that the application wants to fullscreen. https://bugzilla.gnome.org/show_bug.cgi?id=708718
* Bump version to 3.10.0.13.10.0.1Owen W. Taylor2013-09-252-1/+9
| | | | Update NEWS
* MetaWindowActor: fix updates with multiple size changes in one frameOwen W. Taylor2013-09-251-8/+11
| | | | | | | | | | We must set size_changed even if we are frozen, as every window size change makes the X server drop the pixmap, and we might lose the information at the next thaw() if the window changes size twice in one frame (so we would keep drawing with the old pixmap until something else causes another resize) Fix done together with Giovanni Campagna <gcampagn@redhat.com>
* Bump version to 3.10.03.10.0Florian Müllner2013-09-232-2/+9
| | | | Update NEWS.
* Updated Hebrew translationYosef Or Boczko2013-09-231-103/+105
| | | | Signed-off-by: Yosef Or Boczko <yoseforb@gmail.com>
* Updated Portuguese translationDuarte Loreto2013-09-231-349/+305
|
* Fix a typo in Hungarian translationGabor Kelemen2013-09-191-1/+1
|
* Updated Danish translationAsk H. Larsen2013-09-171-292/+248
|
* Bump version to 3.9.923.9.92Florian Müllner2013-09-162-1/+23
| | | | Update NEWS.
* Update .gitignoreFlorian Müllner2013-09-161-0/+1
|
* MonitorConfig: fix hole filling in the laptop lid automatic configurationGiovanni Campagna2013-09-161-2/+5
| | | | | | | | | Need two passes, because the order we traverse the array is alphabetical on connector name, not left to right, so we might see a monitor on the right before we get the offset from disabling the primary monitor. https://bugzilla.gnome.org/show_bug.cgi?id=707473
* MetaIdleMonitor: fire immediately watches that are already expiredGiovanni Campagna2013-09-161-1/+28
| | | | | | | | | | | | | | | | | | The XSync semantics mandate that alarms already expired will not fire until the counter is reset and the alarm triggered again, so clients traditionally called get_idle_time() first to see if they should install the alarm. This is inherently racy, as by the time the call is handled by mutter and the reply received the idle time could be different. Instead, if we see that the watch would have fired in the past, fire it immediately. This is a behavior change, but it's a compatible one, as all legacy clients are calling get_idle_time() first, and it was perfectly possible for the idle time counter to trigger the alarm right after the get_idle_time() call. https://bugzilla.gnome.org/show_bug.cgi?id=707302
* Updated German translationBenjamin Steinwender2013-09-161-322/+288
|
* Add Kazakh translationBaurzhan Muftakhidinov2013-09-162-0/+1478
|
* MonitorConfig: fix memory leakPavel Vasin2013-09-141-0/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=708070
* shaped-texture: Fix memory leakPavel Vasin2013-09-141-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=708070
* window: Fix memory leakPavel Vasin2013-09-141-0/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=708070
* workspace: Add missing chain-up for finalize()Pavel Vasin2013-09-141-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=708070
* Updated Indonesian translationAndika Triwidada2013-09-141-259/+68
|
* Assamese Translation UpdatedNilamdyuti Goswami2013-09-131-275/+224
|
* Updated Belarusian translation.Ihar Hrachyshka2013-09-121-316/+125
|
* Updated Latvian translationRūdolfs Mazurs2013-09-121-272/+226
|
* Fixup previous commitGiovanni Campagna2013-09-121-1/+1
| | | | Had a wrong cursor name.
* display: add support for more cursor typesGiovanni Campagna2013-09-124-8/+49
| | | | | | | | | These cursors are used by gnome-shell, supporting them allows to reduce GDK usage in the shell. Also, make meta_screen_set_cursor() public. https://bugzilla.gnome.org/show_bug.cgi?id=707919
* [l10n] Updated Estonian translationMattias Põldaru2013-09-121-116/+115
|
* MonitorXrandr: Mask a BadValue error on VirtualBox.Colin Guthrie2013-09-111-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=707563
* MetaPluginManager: don't require plugins to pass events to clutterGiovanni Campagna2013-09-104-23/+16
| | | | | | | We don't want the shell to know if it's running on ClutterX11 or not, so we should forward the event ourselves. https://bugzilla.gnome.org/show_bug.cgi?id=707482
* Punjabi Translation updated by AmanA S Alam2013-09-091-270/+223
|
* Rename META_POWER_SAVE_UNKNOWN to UNSUPPORTEDGiovanni Campagna2013-09-093-5/+5
| | | | | | It conveys more clearly what this value means. https://bugzilla.gnome.org/show_bug.cgi?id=707649
* Monitor: don't shortcut set_power_save if the value is the same as the old oneGiovanni Campagna2013-09-091-3/+0
| | | | | | | | | We don't get notifications from X11 when the mode is reset, so our cached value can get stale. To work around that, always forward requests to the backend (and let it deal with ignoring the change if wanted) https://bugzilla.gnome.org/show_bug.cgi?id=707649
* Updated Korean translationChangwoo Ryu2013-09-091-326/+132
|
* Finnish translation update by Jiri GrönroosVille-Pekka Vainio2013-09-071-279/+233
|
* Updated Russian translationYuri Myasoedov2013-09-061-563/+358
|
* Updated Traditional Chinese translation(Hong Kong and Taiwan)Chao-Hsiung Liao2013-09-062-694/+602
|
* Updated Serbian translationМирослав Николић2013-09-062-4/+4
|
* Updated Serbian translationМирослав Николић2013-09-052-638/+248
|
* window-actor: Use more conservative paint volumeAdel Gadllah2013-09-041-0/+3
| | | | | We know which part of the window is not obscured, so take advantaged of that to limit the size of the paint volume that we report.
* MetaCursorTracker: don't ask X to set the cursor visibility to the same valueGiovanni Campagna2013-09-041-0/+4
| | | | | Apparently, that's a Match error. Yay for well designed APIs...
* MetaCursorTracker: add methods for setting the cursor visibilityGiovanni Campagna2013-09-042-0/+14
| | | | | | | | | clutter_stage_show_cursor()/hide_cursor() only works in the X11 backend (where someone else is in charge of showing the cursor), and even then, it has confusing effects when running nested wayland, so an abstraction layer is needed. https://bugzilla.gnome.org/show_bug.cgi?id=707474
* MetaCursorTracker: extend with query pointer abilitiesGiovanni Campagna2013-09-042-0/+27
| | | | | | | We need an abstraction in gnome-shell for XQueryPointer, and MetaCursorTracker seems a good place for it. https://bugzilla.gnome.org/show_bug.cgi?id=707474
* MonitorConfig: remove holes generated by disabling the laptop lidGiovanni Campagna2013-09-041-6/+19
| | | | | | | | No, holes in the framebuffer are not a good a thing: windows can get lost there, and the user can get very confused. Instead, compact the monitors that where previously after. https://bugzilla.gnome.org/show_bug.cgi?id=707473
* Don't create a dummy texture for the texture pipeline templateNeil Roberts2013-09-041-17/+14
| | | | | | | | | | | | | | | | | | | | The meta_create_texture_pipeline function used to create a dummy 1x1 texture so that it could make sure that the all of the state that affects the shader generation would be set on the template pipeline so that Cogl could share the pipeline's shader with any other pipelines that are just rendering a texture. This is no longer necessary because the only thing that affects the shader generation is the texture type, not the actual texture data and Cogl now has a function to explicitly set the texture type which we can use instead. Additionally even if the template mechanism is not used at all Cogl will still end up reusing the same shader because it now has a shader cache which is indexed by the pipeline state so pipeline's don't strictly need to share ancestry in order to take advantage of it. However we still might as well use the function because if there is a common ancestry it is faster to look up the shader because Cogl doesn't need to hash the pipeline state. https://bugzilla.gnome.org/show_bug.cgi?id=707458
* Make sure to always call va_endJasper St. Pierre2013-09-032-3/+8
|
* compositor: Remove some uninitialized variablesJasper St. Pierre2013-09-032-7/+2
|
* theme-parser: Remove a duplicate pasteJasper St. Pierre2013-09-031-3/+0
| | | | How did this sneak in there?
* display: Add some missing breaksJasper St. Pierre2013-09-031-0/+3
| | | | | If we somehow get an event with a wrong device ID, we should not be comparing bad event IDs.
* compositor: initial has_window to FALSE in sync_actor_stackingRay Strode2013-09-031-0/+1
| | | | Spotted by Jasper, discussed on IRC.
* Bump version to 3.9.913.9.91Florian Müllner2013-09-032-1/+23
| | | | Update NEWS.
View Lorry Controller Status