summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Added Occitan translationclutter-1.20Cédric Valmary2016-03-081-0/+2888
|
* Updated Portuguese translationPedro Albuquerque2015-11-241-669/+669
|
* Updated Swedish translationAnders Jonsson2015-09-201-1285/+1595
|
* actor: Use the real opacity when clearing the stageEmmanuele Bassi2015-04-301-1/+7
| | | | | | | | | | | | The paint opacity for a top level is always overridden to be the full value, since it's a composited value and we want to paint our scene. When clearing the stage framebuffer, though, we want to use the actual opacity, if ClutterStage:use-alpha is set. (cherry picked from commit 8b8aa0b4927bc865b08b77b4e28237da0ff8597c) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* clutter-stage-cogl: Match EGL's behavior of eglSwapBuffersWithDamageJasper St. Pierre2015-04-291-5/+1
| | | | | | | | | | | | | | | | | | | -1 is explicitly an invalid value to pass to eglSwapBuffersWithDamage, and the specification admits as much: If eglSwapBuffersWithDamageEXT is called and <n_rects>, is less than zero or <n_rects> is greater than zero but <rects> is NULL, EGL_BAD_PARAMETER is generated. Fix up our usage of SwapBuffersWithDamage to match the behavior in the EGL specification. https://bugzilla.gnome.org/show_bug.cgi?id=745512 (cherry picked from commit 21ce9bc08b72f0904c6b682341481798d05f7d8c) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* Post-release version bump to 1.20.3Emmanuele Bassi2015-04-231-2/+2
|
* Release Clutter 1.20.2 (stable)1.20.2Emmanuele Bassi2015-04-232-2/+34
|
* build: Skip gitignore files when not building from gitEmmanuele Bassi2015-04-231-7/+8
| | | | There's really no point in going through the motions there.
* build: Create .gitignore files in the current directoryEmmanuele Bassi2015-04-231-5/+5
| | | | We cannot touch srcdir when distchecking.
* x11: Improve touchpad detection heuristicsEmmanuele Bassi2015-04-231-1/+33
| | | | | | | | | | | | | | We should use the same heuristics used by GDK in order to detect whether a device is a touchpad or not. Based on the similar code from Carlos Garnacho for GDK: https://git.gnome.org/browse/gtk+/commit/?id=6f07d5e7 https://bugzilla.gnome.org/show_bug.cgi?id=747436 (cherry picked from commit 79849ef1d5fff9acd310cd68d59df0c7cf2cb28f) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* tests: Remove calls to clutter_x11_enable_xinput()Emmanuele Bassi2015-04-234-17/+0
| | | | | The function is deprecated and useless: support for XInput is always enabled, if the extension is available.
* cogl/stage: Fix a compiler warningEmmanuele Bassi2015-04-231-0/+2
|
* build: Use subdir-objectsEmmanuele Bassi2015-04-231-367/+369
| | | | | | (cherry picked from commit e2eb0b0adad71bbd3bd71d5e82288bd9d9c5985d) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: Drop the full path for headersEmmanuele Bassi2015-04-231-8/+2
| | | | We don't need it any more.
* build: Drop ad hoc gitignore generation rulesEmmanuele Bassi2015-04-231-9/+8
| | | | | | | Instead, include Makefile.am.gitignore. (cherry picked from commit 847e3a2c553df8f0a6c78b6c6264a6c77a6e5704) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: Fix up gitignore generation rulesEmmanuele Bassi2015-04-231-1/+3
| | | | | | | | Use more sources, and allow adding files to the ignore list when including Makefile.am.gitignore. (cherry picked from commit 7bfd62f755410a6982a436f3edc938666fe5cdb9) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* Ignore automake droppingsEmmanuele Bassi2015-04-231-0/+1
| | | | | (cherry picked from commit 8d6cab0e71af3b9cb818cdd7b7f815505e2c9fac) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: More out of tree build fixesEmmanuele Bassi2015-04-232-3/+5
| | | | | (cherry picked from commit 2f490c9dcc3111217ddb968054c1c0d5e475564b) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: Fix out-of-tree buildsEmmanuele Bassi2015-04-231-4/+5
| | | | | | | Add a srcdir prefix to the inspected files for glib-mkenums. (cherry picked from commit 8e87d0417b341ca43d9399937c5946fe9cb48c32) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* input-device: Reset the focused actor when it becomes unreactiveJasper St. Pierre2015-04-231-0/+18
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=743865 (cherry picked from commit 6c057e3171607d3cbfa61ec57c1fff6c5d72b14c) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: Add top_builddir to the API reference sourcesEmmanuele Bassi2015-04-231-1/+1
| | | | | | | Otherwise gtk-doc won't be able to find some generated files. (cherry picked from commit 73e6f4e69df1b464c40e4652ed3cffccb003e7bb) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* build: Use libtool macros to find libmEmmanuele Bassi2015-04-238-19/+9
| | | | | | | | | Instead of using `-lm` everywhere, use LT_LIB_M inside configure.ac, and $(LIBM) inside Makefile.am. (cherry picked from commit df15f04fc0474be09e6839618c598d43aee920e5) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* rectangle: Fix the border drawing conditionsEmmanuele Bassi2015-04-231-55/+62
| | | | | | | And reorganize the code a bit while we're at it. (cherry picked from commit ce2d86515a58042011b41066492833d189f3fd1a) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* rectangle: Do not draw the border if bigger than the allocationEmmanuele Bassi2015-04-231-8/+22
| | | | | | | | | | | | | | If the rectangle is allocate a size smaller than the border, drawing the border will end up with negative coordinates, and will mess up the whole thing. Since rectangles don't have a minimum preferred size, we cannot rely on the allocation being big enough to contain the border and the background color. If the rectangle is smaller than the border width value, we just paint the border color as well. (cherry picked from commit 6de341392126e83e098a360b2d77f6259ee09a23) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* stage-cogl: Fix damage tracking with varying buffer agesChris Wilson2015-04-232-59/+54
| | | | | | | | | | | | | | | | | | | | | | | | With server-side buffer allocation, buffers may be returned out of order (e.g. they may be held onto by external references or hardware). As such we may see older buffers the frame after we discard the history from seeing a very young buffer. To overcome this we want to keep the history in a ring so we can keep track of older entries without keeping an unbounded list. After converting to a ring, the maximum buffer age observed during testing was 5 (expected value of 4), but before we could see ages as high as 9 due to the huge latency spikes caused by doing full buffer redraws (compounded by external listeners doing readback on the damaged areas, for example vnc, drm/udl, prime). For this reason, a maximum age of 16 was chosen to be suitably large enough to prevent these worst cases from taxing the system. v2: Fix off-by-one in combining the damage histroy into the clipping rectangle, and apply copious whitespace fixes. Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=745512 References: https://bugzilla.gnome.org/show_bug.cgi?id=724788 References: https://bugzilla.gnome.org/show_bug.cgi?id=669122 (cherry picked from commit 239280f855db26fec93646af51bbc772478ef698) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* stage-cogl: Use swap buffers with damageChris Wilson2015-04-231-21/+31
| | | | | | | | | | | | | cogl provides an interface to pass along damage with the swap buffers request. This is useful for the display servers and hardware to minimise the work done in updating the screen and also reducing the work done by external listeners (such as vnc, drm/udl and PRIME). Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=745512 (cherry picked from commit 55c957267ef241767ebd3891d49f06deb2ff4aa9) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* Updated Turkish translationNecdet Yücel2015-03-211-934/+1725
|
* Added Bosnian translationSamir Ribic2015-03-141-0/+2836
|
* gdk: Use non-deprecated GdkCursor APIEmmanuele Bassi2015-01-091-2/+6
| | | | | | | The non-display safe variant has been deprecated in GTK+ 3.15. (cherry picked from commit 54efcf0e903e50ce927d3b22aa1edfa7dfa1744a) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* gdk: Disable deprecation warningsEmmanuele Bassi2015-01-091-0/+3
| | | | | | | We don't want to break the build because GDK deprecated some symbol. (cherry picked from commit 7d7eb8aabda177e502f388cbe7dd6b2b4e892bc3) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* x11: Resort to device name matching for non-mt touchpadsCarlos Garnacho2015-01-091-0/+2
| | | | | | | | | | If a touchpad is not multitouch, or does not report MT axes (eg. through the libinput driver), resort to name matching before falling back to CLUTTER_POINTER_DEVICE. https://bugzilla.gnome.org/show_bug.cgi?id=741350 (cherry picked from commit a0e2ba62a185c2db1fb998863f3e2011aebfaf68) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* Easing modes are not used when computing the value of a KeyframeTransitionSamuel Degrande2015-01-091-2/+2
| | | | | | | | | | | | | | An easing mode can be set on a frame of a KeyframeTransition. However, the progress value of the current frame is computed using using a linear function. This patch adds a call to clutter_easing_for_mode() to compute the actual progress value. Note that parametrized easing modes (bezier and 'step') are not taken into account. https://bugzilla.gnome.org/show_bug.cgi?id=740997 (cherry picked from commit e7d1458298318dad8eb046540162323dc1a76b25) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* actor: Bail when setting the same contentEmmanuele Bassi2015-01-091-0/+3
| | | | | | | No need to do all the work, if the content instance is the same. (cherry picked from commit 1e2132eca49347a2d8e519ab45780c52952c3e9e) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* actor: Reset the content box when setting a new contentEmmanuele Bassi2015-01-091-1/+19
| | | | | | | | | | | We want to recompute the content box when changing the content instance, in case the preferred size is different and the content gravity uses the preferred size; the change of content with different preferred size and same gravity should also trigger an implicit transition. https://bugzilla.gnome.org/show_bug.cgi?id=711182 (cherry picked from commit d546c0c121a967ab49773f91119dffe9d0358cdd) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* conform: Drop a deprecated propertyEmmanuele Bassi2015-01-091-1/+1
| | | | | | | | Use the non-deprecated :orientation property, instead of the deprecated :vertical one. (cherry picked from commit e6a60f661784f3c0d8744402a0569ea47426ba02) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* script: Do not overwrite ObjectInfo fieldsEmmanuele Bassi2015-01-091-9/+10
| | | | | | | | | | | | When merging multiple definitions it's possible that the ObjectInfo fields may get overwritten. Instead of trampling over the fields, we should reset them only when they actually change — especially the "is_actor" one, which controls the destruction of the objects when unmerging happens. https://bugzilla.gnome.org/show_bug.cgi?id=669743 (cherry picked from commit d005c6a8809fe48ce5c8e5a9f0f620e4f60bb7e6) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* device-manager-xi2: Fix core pointer retrieval raceSjoerd Simons2015-01-092-23/+17
| | | | | | | | | | | | | | | | | | | | | | | | The core pointer concept doesn't really exist anymore in an XI2 world, so the clutter API is a bit of a mismatch with what X provides. Using XIGetClientPointer doesn't really help, as far as i can tell the semantics of XIGetClientPointer are essentially: Whatever the X server picked when it had to reply with device-dependant data to a query without a device specifier. Not very useful... To make matters worse, whether XIGetClientPointer returns a valid pointer depends on whether there has been a query that forced it to pick one in the first place, making the whole thing pretty non-deterministic. This patch changes things around such that instead of using XIGetClientPointer to determine the core pointer, we simply pick the first master pointer device. In practise this will essentially always be the X virtual core pointer. https://bugzilla.gnome.org/show_bug.cgi?id=729462 (cherry picked from commit 1be019852f0a64188df3d4e45820246f21fdacbe) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* device-manager-xi2: Fix scaling of coordinatesJonas Danielsson2015-01-091-2/+2
| | | | | | | | | Do not CLAMP to width/height before applying the scale factor we will lose all information we need to scale properly. https://bugzilla.gnome.org/show_bug.cgi?id=730815 (cherry picked from commit 9660b001f7ee410bcbff545989a708b103e6faaf) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* evdev: Prefer pointer/touch devices over keyboard devicesCarlos Garnacho2014-12-101-3/+3
| | | | | | | | | | | | | | In keyboard/mouse wireless combos, it is rather common for the mouse to claim it contains the multimedia keys, this makes libinput enable both the pointer and keyboard capabilities on this device, and Clutter thus to create a keyboard ClutterInputDevice for it. Ideally clutter devices should be able to reflect their full capabilities, or maybe account for the fact that certain events can be sent from seemingly unexpected device types. But this will bring a somewhat better behavior on such devices. https://bugzilla.gnome.org/show_bug.cgi?id=740518
* Revert "actor: Plug a leak in the implicit transition removal"Emmanuele Bassi2014-11-261-8/+0
| | | | | | | This reverts commit 158af1ff594d8984b59dcf90654ed04cd8c53e16. This commit introduced a regression, so the leak will have to be fixed in another way.
* actor: Create a PangoContext per actorJasper St. Pierre2014-10-233-88/+60
| | | | | | | | | | | | | | | | For a variety of complicated reasons, ClutterText currently sets fields on the PangoContext when creating a layout. This causes ClutterText to behave somewhat erratically in certain cases, since the PangoContext is currently shared between all actors. GTK+ creates a PangoContext for every single GtkWidget, so it seems like we should do the same here. Move the private code that was previously in clutter-main.c into clutter-actor.c and clean it up a bit. This gives every actor its own PangoContext it can mutilate whenever it wants, at its heart's content. https://bugzilla.gnome.org/show_bug.cgi?id=739050
* main: Don't update the PangoContext in clutter_set_font_flagsJasper St. Pierre2014-10-231-5/+0
| | | | | | | | clutter_set_font_flags already calls clutter_backend_set_font_options, which emits a signal which our PangoContext listens to, so this is just duplicate and unneeded code. https://bugzilla.gnome.org/show_bug.cgi?id=739050
* evdev: Flush event queue before removing an input deviceCarlos Garnacho2014-10-141-0/+17
| | | | | | | | | | | | | libinput_suspend() will trigger the removal of input devices, but also the emission of button/key releases pairing everything that is pressed at that moment. These events are queued, but the ClutterInputDevice pointers in these will point to invalid memory at the time these are processed. Fix this by flushing the event queue, in order to ensure there are no unprocessed input events after libinput_suspend(). https://bugzilla.gnome.org/show_bug.cgi?id=738520
* x11: Add missing closure annotation to ClutterX11FilterFuncRico Tzschichholz2014-10-021-1/+1
|
* build: Update the release rulesEmmanuele Bassi2014-09-221-10/+10
| | | | | Change the URLs for mailing lists and documentation, and re-align the output.
* Post-release version bump to 1.20.1Emmanuele Bassi2014-09-221-2/+2
|
* Release Clutter 1.20.01.20.0Emmanuele Bassi2014-09-222-2/+14
|
* docs: Fix the examples for ClutterText.set_font_name()Emmanuele Bassi2014-09-221-1/+6
| | | | | | | We shouldn't be using "pt": PangoFontDescription.from_string() assumes points, and only accepts "px" for absolute font sizes. https://bugzilla.gnome.org/show_bug.cgi?id=736826
* docs: Update the markdown README fileEmmanuele Bassi2014-09-221-19/+11
|
* Updated Greek translationMaria Mavridou2014-09-211-154/+153
|
View Lorry Controller Status