| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Added support for Mir, now clutter can natively draw on MirSurfaces.
This depends on latest cogl git.
Run your clutter apps using CLUTTER_BACKEND=mir
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
We have a bunch of versions to cover.
|
|
|
|
| |
The 1.22 cycle did start a while ago.
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Check a touchpad-only setting, and if it returns an expected value there,
the device must be a CLUTTER_DEVICE_TOUCHPAD.
https://bugzilla.gnome.org/show_bug.cgi?id=741350
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
Atlasing is fine for smaller textures, but once they get too large its
downsides outweight the benefits. At worst, the larger texture will end
up inside its own atlas, but at worst it will require copying and/or
resizing of an existing atlas.
The cut-off at 512x512 pixels is a bit arbitrary, and we can change it
at any point; it would be nice if we could get the texture limit from
Cogl, and then use a fraction of that size as the cut-off limit. Sadly,
that's not portable, and it's not guaranteed to work either.
|
|
|
|
| |
The non-display safe variant has been deprecated in GTK+ 3.15.
|
|
|
|
| |
We don't want to break the build because GDK deprecated some symbol.
|
|
|
|
| |
Initialize a pointer variable.
|
|
|
|
|
|
|
| |
This reverts commit 158af1ff594d8984b59dcf90654ed04cd8c53e16.
This commit introduced a regression, so the leak will have to be fixed
in another way.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
Change the URLs for mailing lists and documentation, and re-align the
output.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The Returns: stanza is missing.
|
| |
|
|
|
|
|
| |
The API is public because we use it in the test suite, but it's not
documented.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
We already check for needs_allocation before getting the default paint
volume, but explicit is better than implicit.
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=734480
|
|
|
|
|
|
| |
So that we follow GDK's idea of a scaling factor for Clutter.
https://bugzilla.gnome.org/show_bug.cgi?id=734480
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Both backends are built via CI and used by GNOME, so they should not be
considered experimental any more.
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|