summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release Clutter 1.25.2 (snapshot)1.25.2Emmanuele Bassi2015-12-172-2/+58
|
* docs: Add 1.26 symbols indexEmmanuele Bassi2015-12-171-0/+5
|
* docs: Update sections file for missing macrosEmmanuele Bassi2015-12-171-0/+6
|
* Updated Slovenian translationMatej Urbančič2015-12-131-253/+253
|
* Updated Portuguese translationPedro Albuquerque2015-12-131-269/+266
|
* build: Rework the default rules for the EGL backendEmmanuele Bassi2015-12-111-51/+47
| | | | | | | | | So that we can set it to 'check', and do configure-time discovery of the dependencies, instead of enabling it explicitly. This should make it easier to spot build issues on environments like Continuous, which build Clutter and Cogl for running as part of the display server infrastructure on Wayland.
* egl: Rename backend constructor functionEmmanuele Bassi2015-12-111-1/+1
| | | | Otherwise the build will fail.
* tests: Force X11 backend for the pixmap testEmmanuele Bassi2015-12-111-0/+4
| | | | | | So it's usable as long as the X11 backend support is compiled into Clutter — and we can use this test to check that overriding works as intended.
* Allow setting the default backend from the configuration fileEmmanuele Bassi2015-12-113-0/+20
| | | | | | | | | | We should allow a configuration file to set up the initial state of the global state, which also implies being able to set the backend. If the allowed backends have already been set programmatically via the clutter_set_windowing_backend(), though, then the application code takes precedence, as we assume that the application author knows better than us what their code supports or requires.
* Read the config file when creating the global shared stateEmmanuele Bassi2015-12-111-6/+6
| | | | | | | The configuration file should set up the global state before we initialize it; instead of relying on implicit ordering, explicitly read the configuration file once, when creating the global shared context data structure.
* backend: Ensure that Cogl drivers are set prior to initializationEmmanuele Bassi2015-12-111-0/+6
| | | | | It doesn't make sense for the allowed drivers to be changed after Clutter has been initialized.
* backend: Allow setting a list of windowing backendsEmmanuele Bassi2015-12-111-43/+93
| | | | | | | | | | | Like CLUTTER_DRIVER, we want to allow users to specify a list of backends to test, and fall back to the internally defined priority as a default. This requires changing the way the allowed backend string is parsed, both for the CLUTTER_BACKEND environment variable and for the clutter_set_windowing_backend() function. Existing callers are still supported with the exact same semantics.
* Add internal constructor function for each backendEmmanuele Bassi2015-12-1114-21/+67
| | | | | We're going to use it to create an instance of each backend without using the get_type() function.
* Allow overriding the list of Cogl drivers via configuration fileEmmanuele Bassi2015-12-103-1/+19
| | | | | Clutter has a configuration file that can be used to override various settings, including the ones from environment variables.
* Add a configuration option for deciding the Cogl drivers to useEmmanuele Bassi2015-12-102-1/+10
| | | | | | | | | | Using environment variables only is not convenient for all platforms, and in some cases it's beneficial to decide the default driver when building Clutter. Cogl already has a similar configuration switch, and since Clutter is overriding the default Cogl behaviour, it should offer the same mechanism. https://bugzilla.gnome.org/show_bug.cgi?id=742678
* backend: Allow overriding the Cogl drivers chainEmmanuele Bassi2015-12-102-23/+73
| | | | | | | | | | | | | | | | | | We have an hardcoded list of drivers we have to go through when creating a Cogl context. Some platforms may expose those drivers, but not be the preferred ones. In order to allow users and system integrators to override the list of drivers, we should crib the same approach used by GDK, and have an environment variable with a list of drivers to try. The new environment variable is called `CLUTTER_DRIVER` and accepts a comma-separated list of driver names, which will be tested in sequence until one succeeds. There's also an additional '*' token which is used to ask Clutter to fall back to the internally defined preferred list of drivers. https://bugzilla.gnome.org/show_bug.cgi?id=742678
* Fix annotation for bind_model()Emmanuele Bassi2015-12-091-1/+1
| | | | | The (optional) annotation should only be used for (out) arguments; in arguments that can be NULL should use the (nullable) annotation.
* Fix definition of ClutterEventExtenderEmmanuele Bassi2015-12-091-0/+2
| | | | | The interface vtable structure is missing the GTypeInterface parent, and GObject is complaining about it, as it should.
* build: Use the 'x11' pkg-config module to check for X11Emmanuele Bassi2015-12-081-4/+1
| | | | | | Don't look at GLX headers or symbols; we don't use them anyway. https://bugzilla.gnome.org/show_bug.cgi?id=759191
* gdk: Check for both GDK and Cogl winsys supportEmmanuele Bassi2015-12-081-3/+3
| | | | | | When using GDK and Cogl API, we need to check that both GDK and Cogl have been built with support for that API, otherwise the build will likely fail.
* test: interactive: port cairo clock to ClutterCanvasLionel Landwerlin2015-12-061-16/+16
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=759074
* test: interactive: port cairo flowers to ClutterCanvasLionel Landwerlin2015-12-061-11/+30
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=759074
* evdev: Drop redundant stage set checkJonas Ådahl2015-12-031-5/+0
| | | | | | | Every path creating a input device in the evdev backend sets a stage, so the check is unnecessary. https://bugzilla.gnome.org/show_bug.cgi?id=752752
* text: Enforce boolean valueEmmanuele Bassi2015-11-301-0/+2
| | | | | | We store the cursor-visible value in a bit field, which means that we need to enforce the argument for the setter to either 0 or 1 in order to fit.
* docs: Improve documentation for ClutterTextEmmanuele Bassi2015-11-301-3/+8
| | | | Ensure that the rule for :cursor-visible are documented.
* text: Unify conditions for visible cursorEmmanuele Bassi2015-11-301-12/+6
| | | | | We have a bunch of similar checks in various places, and they should all be coalesced into one.
* build: Add --disable-WerrorEmmanuele Bassi2015-11-301-12/+21
| | | | | | | | | | | We enable a bunch of compiler flags to trip common errors during development. While this is very useful while hacking on Clutter, it makes the life of people building Clutter on automated build systems much harder; thus, we should have a configuration option to opt out of the -Werror business. GNOME has pretty much standardised on `--disable-Werror`, so we should crib that configure option.
* Add tags to the Git ignore fileEmmanuele Bassi2015-11-281-0/+1
|
* text: Allow selectability without editabilityEmmanuele Bassi2015-11-281-70/+75
| | | | | | | | | | | | | | | | | | | | | | | Being able to select text and being able to edit text are two separate capabilities, but ClutterText only allows the former with the latter. The ClutterText:selectable property is set to TRUE by default, given that it depends on the :editable property; this implies that all ClutterText instances now are going to show a cursor as soon as they get key focused. Obviously, this would make labels look a bit off — but if you have a label then you would not give it key focus, either by explicitly calling clutter_actor_grab_focus(), or by setting it as reactive and allowing it to be clicked. If this turns out to be a problem, we have various ways to avoid showing a cursor — for instance, we could change the default value of the selectable property, and ensure that setting the :editable property to TRUE would also set the :selectable property as a side effect. Or we could hide the cursor until the first button/touch press event. Finally, we could always back this commit out if it proves to be too much of a breakage for existing code bases. https://bugzilla.gnome.org/show_bug.cgi?id=757470
* gdk: take into account scaling on waylandLionel Landwerlin2015-11-221-20/+30
| | | | | | | | The X11 part of the GDK backend takes into account the scaling factor of its window when resizing the underlying X11 objects. We need to do the same for Wayland. https://bugzilla.gnome.org/show_bug.cgi?id=755245
* gdk: Implement ClutterEventExtenderCarlos Garnacho2015-11-182-26/+36
| | | | | | This lifts the responsibility off its ClutterBackend. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* x11: Implement ClutterEventExtenderCarlos Garnacho2015-11-182-26/+34
| | | | | | This lifts the responsibility off its ClutterBackend. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* evdev: Set event code on button/key eventsCarlos Garnacho2015-11-181-0/+3
| | | | | | | This will allow users to know the event code without strange calculations on event->key.hardware_keycode or event->button.button. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* evdev: Allow to retrieve the input.h event code from ClutterEventsCarlos Garnacho2015-11-185-0/+123
| | | | | | | | This is now stored as platform data in the ClutterEvent, so can be retrieved with the clutter_evdev_event_get_event_code() call that's been added to the evdev backend. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* evdev: Implement the ClutterEventExtender interfaceCarlos Garnacho2015-11-181-3/+28
| | | | | | | This will allow the ClutterDeviceManagerEvdev to define evdev-specific event data. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* backend: Bridge platform-dependent event data creation to device managersCarlos Garnacho2015-11-181-2/+18
| | | | | | | | Device managers can now implement the ClutterEventExtender interface that allows them to set their own data to events, make the backend call those implementations if the device manager implements the interface. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* device-manager: Add private interface to manipulate platform event dataCarlos Garnacho2015-11-182-0/+29
| | | | | | | | | | | This normally belonged to the ClutterBackend, however there's device managers (eg. evdev) that are somewhat detached from the backend, so need to bridge this somehow. This allows device managers to implement these bits that were usually responsibility of the ClutterBackend. https://bugzilla.gnome.org/show_bug.cgi?id=758238
* Add version macros for Clutter 1.26Emmanuele Bassi2015-11-182-0/+28
|
* Bump up version to 1.25.1Emmanuele Bassi2015-11-181-2/+2
|
* evdev: Move additional pointer buttons after the old 4-7 scrolling onesCarlos Garnacho2015-11-171-2/+3
| | | | | | | | On X11 those were skipped, so additional pointer buttons would come up as button >= 8 events. Do here the same, so we remain compatible across backends. https://bugzilla.gnome.org/show_bug.cgi?id=758237
* update zh_CN translationJeff Bai2015-11-141-585/+600
|
* update zh_CN translationYunQiang Su2015-11-041-37/+24
|
* evdev: Mark either of smooth/discrete scroll events as emulatingCarlos Garnacho2015-10-231-7/+16
| | | | | We're always emulating one of those, depending on the scrolling device/source, so mark these as such.
* click-action: Ignore motions/updates from different devices/sequencesCarlos Garnacho2015-10-171-0/+4
| | | | | | | Otherwise events from other devices or touch sequences might unintendedly trigger the thresholds, and a "cancelled" ::long-press with it. https://bugzilla.gnome.org/show_bug.cgi?id=756749
* Updated Basque languageInaki Larranaga Murgoitio2015-10-141-438/+438
|
* Post-release version bump to 1.24.3Emmanuele Bassi2015-10-121-2/+2
|
* Release Clutter 1.24.21.24.2Emmanuele Bassi2015-10-122-2/+28
|
* Use explicit NULL comparison for pointersEmmanuele Bassi2015-10-121-11/+11
| | | | Following the coding style.
* evdev: Emulate discrete scroll events out of smooth scroll ones.Carlos Garnacho2015-10-121-8/+122
| | | | | | | | | | | | | | | | There's handlers around relying on up/down/left/right scroll events, which won't work as expected if only smooth scroll events are sent. In order to work properly there, we have to retrofit discrete scroll events on the evdev backend. Fix this by implementing emission (on devices with a wheel) and emulation (on anything else) of discrete scroll events. On the former both smooth and discrete events are set, for the latter we do accumulate the dx/dy of the latest scroll events, and emit discrete ones when we accumulated enough. The ending 0/0 event will reset the accumulators for the next scrolling batch. https://bugzilla.gnome.org/show_bug.cgi?id=756284
* Updated Portuguese translationPedro Albuquerque2015-10-071-12/+12
|
View Lorry Controller Status