summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* doap category coreOlav Vitters2014-09-191-0/+1
|
* Post-release version bump to 1.19.11Emmanuele Bassi2014-09-171-1/+1
|
* Release Clutter 1.19.101.19.10Emmanuele Bassi2014-09-172-1/+39
|
* docs: Fix annotation for has_mapped_clones() methodEmmanuele Bassi2014-09-171-1/+3
| | | | The Returns: stanza is missing.
* docs: Remove missing symbolEmmanuele Bassi2014-09-171-1/+0
|
* Remove gtk-doc tags from clutter_test_* APIEmmanuele Bassi2014-09-171-6/+6
| | | | | The API is public because we use it in the test suite, but it's not documented.
* actor: Unallocated children do not contribute to the paint volumeEmmanuele Bassi2014-09-151-1/+7
| | | | | | | | | | | | | Just like unmapped children. Apparently, layers above Clutter allow mapped children without an allocation, instead of unmapping them. This means we need to ignore them when computing the paint volume. Patch originally by: Adel Gadllah <adel.gadllah@gmail.com> Signed-off by: Emmanuele Bassi <ebassi@gnome.org> https://bugzilla.gnome.org/show_bug.cgi?id=736682
* actor: Default paint volume does not work without allocationEmmanuele Bassi2014-09-151-0/+6
| | | | | We already check for needs_allocation before getting the default paint volume, but explicit is better than implicit.
* build: Ignore private header while building docsEmmanuele Bassi2014-09-151-0/+1
|
* ClutterInputDevice: Store the cursor coordinate state as floating pointJonas Ådahl2014-09-142-8/+8
| | | | | | | | To support sub-pixel motion events coming from relative events, the fraction part needs to be stored in the input device state as well. To do this, simply change the current type from gint to gfloat. https://bugzilla.gnome.org/show_bug.cgi?id=736413
* a11y: provide a way to ensure clutter accessibilityAlejandro Piñeiro2014-09-033-10/+17
| | | | | | | | | | | | If gtk_init is called after clutter_init, it can override clutter AtkUtil implementation. In that situation, we can't say that the accessibility is enabled, as the root object would be wrong. In order to provide a way to prevent this: * clutter_get_accessibility_enabled returns true of false depending on the current AtkUtil implemented * cally_accessibility_init always override AtkUtil implementation.
* doc: Document CLUTTER_SCALE envvarBastien Nocera2014-09-031-0/+7
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=734480
* gdk: Add window-scaling-factor supportBastien Nocera2014-09-031-0/+1
| | | | | | So that we follow GDK's idea of a scaling factor for Clutter. https://bugzilla.gnome.org/show_bug.cgi?id=734480
* Re-introduce removed GestureAction methodEmmanuele Bassi2014-09-033-2/+24
| | | | | | | | | The get_threshold_tigger_egde() method was renamed to fix the typo, but it obviously broke the ABI. To be fair, nobody in the whole of Debian was using the symbol, apparently, so it's not like we broke existing code. Still, it's not nice to break ABI without bumping soname, so let's put the old symbol back in — obviously, deprecated — as a wrapper to the newly added one.
* Add TestEnvironment key to the installed tests launchersEmmanuele Bassi2014-08-291-0/+1
| | | | | | | | | | The TestEnvironment key allows us to control the environment used by the gnome-desktop-testing-runner harness. We use it to disable the diagnostic messages without having to tweak the Exec line. https://bugzilla.gnome.org/show_bug.cgi?id=734115
* Updated Hebrew translationYosef Or Boczko2014-08-281-482/+494
|
* xi2: XSync before getting the client pointer on constructionCarlos Garnacho2014-08-251-0/+1
| | | | | | | | | | | If the device manager is created and queried for the client pointer at a very early stage in application lifetime, the device_id returned would be 0 as the server hasn't apparently decided yet about the client pointer. For these situations, doing XSync prior to fetching the client pointer gets the server to device about the client pointer before we query it. https://bugzilla.gnome.org/show_bug.cgi?id=735388
* clutter-settings: Mark window-scaling-factor as fixed when set by the appAdel Gadllah2014-08-234-10/+37
| | | | | | | | | | | When an application sets the scaling factor manually we should mark it as fixed and not override it when the xsettings change. This matches GDKs behaviour. In order for this to work we cannot use the same path when setting the value internally so introduce a _clutter_settings_set_property_internal and use it for that. https://bugzilla.gnome.org/show_bug.cgi?id=735244
* Forgot to commit the NEWS file prior to releaseEmmanuele Bassi2014-08-211-0/+27
|
* Post-release version bump to 1.19.9Emmanuele Bassi2014-08-211-1/+1
|
* Release Clutter 1.19.81.19.8Emmanuele Bassi2014-08-211-1/+1
|
* docs: Add missing symbols to the section fileEmmanuele Bassi2014-08-211-0/+2
|
* evdev: Fix compiler warningEmmanuele Bassi2014-08-211-1/+1
|
* build: Remove experimental notice for wayland/evdevEmmanuele Bassi2014-08-211-3/+0
| | | | | Both backends are built via CI and used by GNOME, so they should not be considered experimental any more.
* actor: Plug a leak in the implicit transition removalSunjin Yang2014-08-211-0/+8
| | | | | | | | | We need to release the temporary reference we acquired in order for the signal emission to work. https://bugzilla.gnome.org/show_bug.cgi?id=734761 Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* Updated Assamese translationngoswami2014-08-181-555/+620
|
* Updated German translationChristian Kirbach2014-08-181-51/+40
|
* backend: gdk: add support for foreign windows on waylandLionel Landwerlin2014-08-171-0/+11
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=734935
* backend: gdk: add translation code for touch eventsLionel Landwerlin2014-08-171-0/+27
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=734934
* Revert "backend: try gdk backend before x11/wayland/egl"Emmanuele Bassi2014-08-151-5/+5
| | | | | | | | | | This reverts commit 398a7ac71333208e31d67f3ce50514fab58ba1bb. We cannot really use the GDK backend without massive regressions inside the input layer, like touch events and gestures. The GDK backend is not entirely up to scratch, and it's late in the cycle. Let's land this early in 3.15, and get it up to par with X11.
* Remove unused internal 'in-resize' flagEmmanuele Bassi2014-08-153-17/+2
| | | | A remnant of days gone by.
* backend: try gdk backend before x11/wayland/eglLionel Landwerlin2014-08-101-5/+5
| | | | | | | | | | | | | | Quite a few people at Guadec complained of pinpoint being broken in speaker+fullscreen mode, with slides being half displayed. It turns out that the X11 backend of clutter was being used and this backend assumes the size of the current monitor is the size of the X screen (that's not the case with multiple monitors). To work around the shortcomings of the X11 backend we should probably position the GDK one before. GDK implements most of the logic the ClutterStage needs and is probably more tested. https://bugzilla.gnome.org/show_bug.cgi?id=734587
* evdev: Add API to set the xkb layout indexRui Matos2014-08-072-0/+36
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=733202
* canvas: assign white to paint color for texture nodeTom Beckmann2014-07-251-3/+3
| | | | | | | | To get correct premultiplied opacity on a canvas content, white needs to be assigned to the color that is passed to the texture node. The content will be very dark for lower opacity values otherwise. https://bugzilla.gnome.org/show_bug.cgi?id=733385
* Post-release version bump to 1.19.7Emmanuele Bassi2014-07-241-1/+1
|
* Release Clutter 1.19.6 (snapshot)1.19.6Emmanuele Bassi2014-07-243-1/+40
|
* conform: Fix actor-shader-effectEmmanuele Bassi2014-07-241-1/+2
| | | | | The porting to the ::after-paint signal was missing the boolean flag passed as a user data.
* input-device: Ensure crossing events are paired for touch sequencesCarlos Garnacho2014-07-231-0/+1
| | | | | | | When the sequence is lifted the actor wouldn't be unset, so the corresponding CLUTTER_LEAVE event would never be sent for the touch sequence. https://bugzilla.gnome.org/show_bug.cgi?id=733560
* evdev: Update xkb state after input is resumedCarlos Garnacho2014-07-231-27/+46
| | | | | | | | | xkb_state creation has been refactored out of clutter_evdev_set_keyboard_map(), and used too in clutter_evdev_reclaim_devices(), so the xkb_state is fresh clean after input is paused/resumed (and keyboard state possibly changed in between) https://bugzilla.gnome.org/show_bug.cgi?id=733562
* event: define a boxed type for ClutterEventSequenceCarlos Garnacho2014-07-232-0/+21
| | | | | | This allows for some minimal interaction from bindings. https://bugzilla.gnome.org/show_bug.cgi?id=733561
* ClutterAnimation: fix memory leakGiovanni Campagna2014-07-171-0/+6
| | | | | | We need to unref the timeline https://bugzilla.gnome.org/show_bug.cgi?id=733300
* evdev: Set button modifier state to input devices.Carlos Garnacho2014-07-111-1/+2
| | | | | | | Input devices must get the proper button state, in addition to keyboard modifiers. https://bugzilla.gnome.org/show_bug.cgi?id=733062
* gesture-action: Prepare for clutter_gesture_action_cancel() within ::gesture-endCarlos Garnacho2014-07-081-1/+4
| | | | | | | | | There may be odd situations where full gesture cancellation may be wanted at once when the first touch is lifted and ::gesture-end is emitted on a gesture action. Although calling clutter_gesture_action_cancel() within the ::gesture-end handler causes 2 critical warnings that are otherwise harmless. https://bugzilla.gnome.org/show_bug.cgi?id=732907
* ClutterStage: Replace clutter_stage_set_paint_callback() with ::after-paint ↵Owen W. Taylor2014-06-275-60/+23
| | | | | | | | | | | | signal clutter_stage_set_paint_callback() has the disadvantage that it only works for a single caller, and subsequent callers will overwrite and break previous callers. Replace it with an ::after-paint signal that is emitted at the same point - after all painting for the stage is completed but before the drawing is presented to the screen. https://bugzilla.gnome.org/show_bug.cgi?id=732342
* Post-release version bump to 1.19.5Emmanuele Bassi2014-06-251-1/+1
|
* Release Clutter 1.19.4 (snapshot)1.19.4Emmanuele Bassi2014-06-252-1/+24
|
* gesture-action: Use event type getterEmmanuele Bassi2014-06-251-6/+10
| | | | Don't use direct struct access.
* gesture-action: Ignore any other event than press/update/release onesCarlos Garnacho2014-06-251-0/+5
| | | | | | | | CLUTTER_ENTER/LEAVE might be processed too, leading to accounting of the NULL sequence (ie. pointer) in the gesture, and fooling the gesture with a static extra point that wouldn't go away. https://bugzilla.gnome.org/show_bug.cgi?id=732235
* x11: Set the input device stage on XI_TouchBegin, if not already setCarlos Garnacho2014-06-251-0/+8
| | | | | | | | | | | | | Until now, touch events sort of rely on XI_Enter/XI_Leave events accompanying the pointer emulating touch in order to have a stage set on the device, These events won't happen though if it's not a pointer emulating touch which happens on the stage, causing touch events to be ignored. Fix this by ensuring that the input device has a stage on XI_TouchBegin itself, but only if it's not already set, so we don't possibly steal touch events to an already interacting stage. https://bugzilla.gnome.org/show_bug.cgi?id=732234
* input-device: Do not unset the device stage after the last touch is liftedCarlos Garnacho2014-06-251-3/+0
| | | | | | | | | On X11 the pointer will follow a "pointer emulating" touch sequence, so the pointer will be effectively left inside the stage after that touch is lifted, even though the master device stage is unset. This makes pointer events get ignored until the pointer leaves and enters again the stage. https://bugzilla.gnome.org/show_bug.cgi?id=732234