| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
We were trying to copy motion axes instead of touch ones.
https://bugzilla.gnome.org/show_bug.cgi?id=675371
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some of the Clutter code was using GL types for the primitive types
such as GLint and GLubyte and then passing these to Cogl. This doesn't
make much sense because the Cogl functions directly take native C
types. This patch just replaces them with either a native C type or a
glib type.
Some of the cogl conformance tests are trying to directly call GL for
example to test creating a foreign texture. These tests have been
changed to manually define the GL enum values instead of relying on a
GL header to define them.
This is necessary because Cogl may soon stop including a GL header
from its public headers.
Reviewed-by: Emmanuele Bassi <ebassi@linux.intel.com>
(cherry picked from commit c9a81f035e0ec2d5726497b986ab7469f4de7a74)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The introspection scanner has become slightly more annoying, in the hope
that people start fixing their annotations. As it turns out, it was the
right move.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a further conditional check for calling
clutter_actor_show() when adding a child to an actor. We cannot
unconditionally change the value of the show-on-set-parent property like
the original solution of commit 81b19a78f5e02ae8ffd9235054d80b172496415b
as that breaks the document invariant that show-on-set-parent will be
changed iff an actor is without a parent.
The new ADD_CHILD_SHOW_ON_SET_PARENT flag is part of the default and
legacy flags, thus retaining the default behaviour when adding a child;
the flag is not passed when reordering the list of children, which means
we ignore the state of the show-on-set-parent property.
The conformance test suite fully passes, including the newly added test
to verify that changing the paint order does not trigger visibility.
https://bugzilla.gnome.org/show_bug.cgi?id=674510
|
|
|
|
|
|
| |
Namely, visibility and show-on-set-parent.
https://bugzilla.gnome.org/show_bug.cgi?id=674510
|
|
|
|
|
|
|
| |
When a device is added or changes, select/unselect events from X
accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=673644
|
|
|
|
|
|
|
| |
I.e. only select events for core devices or devices explicitly enabled
by clients.
https://bugzilla.gnome.org/show_bug.cgi?id=673644
|
|
|
|
|
|
|
|
|
|
|
|
| |
The get_distance() API uses machine integers to compute the distance;
this means that on 32bit we can overflow the integer size. This gets
hidden by the fact that get_distance() returns an unsigned integer as
well.
In reality, ClutterPath is an unmitigated mess, and the only way to
actually fix it is to break API.
https://bugzilla.gnome.org/show_bug.cgi?id=652521
|
| |
|
| |
|
| |
|
|
|
|
| |
Up/down is Y.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Drop a bunch of variables that are not meant to be used by Cally; also,
drop the wrong library name from the Libs key: Clutter has a single
shared library, now.
https://bugzilla.gnome.org/show_bug.cgi?id=674105
|
|
|
|
|
|
|
| |
When removing the last Action, Constraint, or Effect, we should also be
clearing the corresponding MetaGroup: code inside ClutterActor relies on
NULL checks, and changing them all to check for NULL && n_items == 0
would not be fun.
|
|
|
|
|
| |
Unmapped children won't be painted so they should not contribute to the
default paint volume computation.
|
|
|
|
|
|
|
| |
Static text shouldn't need a cursor position or anything like that,
and it always eats a button press event.
https://bugzilla.gnome.org/show_bug.cgi?id=673190
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
configure.ac defines XINPUT_2_2 if XI 2.2 support was found. The code
expects XINPUT_2_2 in the device manager, but HAVE_XINPUT_2_2 in the x11
backend.
On newer X servers, the latter causes a BadValue when XIQueryDevice sends a
different major/minor than gdk's device manager (gnome-control-center).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
https://bugzilla.gnome.org/show_bug.cgi?id=673961
|
|
|
|
|
|
| |
We need to remove the transition only if the current repeat is equal to
the number of repeats, and if the transition was marked as remove on
complete. Otherwise, the transition has to remain where it is.
|
|
|
|
|
| |
Since it's in a debug code path, and 1.10 is the stable branch, we
should not bump the dependency of Pango to 1.30.
|
|
|
|
| |
They will be handled internally.
|
|
|
|
|
|
|
| |
The opacity internal setter will do it for us, and it will take into
consideration any eventual flatten effect applied to the actor.
This unbreaks the actor-offscreen-redirect conformance test.
|
|
|
|
|
|
| |
This ensures that constraints and signal handlers will go through the
allocation and not through the cache after ::fullscreen has been
emitted.
|
|
|
|
|
| |
Don't do unprotected calls to set_easing_mode() and
set_easing_duration().
|
|
|
|
|
| |
Let's start making some non-trivial property animatable, like the
content gravity.
|
|
|
|
|
|
| |
When the easing state has a duration of zero milliseconds we can skip
the entire create_transition() call inside set_width() and set_height(),
to avoid what may be a costly call to get_preferred_*.
|
|
|
|
|
| |
When updating a transition in flight, if the current easing state does
not match the transition's.
|
| |
|
|
|
|
|
|
| |
If we update a transition that is currently playing, we need to check
the current easing state, and look at the eventual duration, in case
the user wants to cancel the transition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of checking the duration of the current easing state we should
check if there's a transition in progress, and update it
unconditionally.
If there is no easing state, or the easing state has a duration of zero
milliseconds, then create_transition() should bail out early and set the
requested final state.
This allows us to write:
clutter_actor_save_easing_state (actor);
clutter_actor_set_x (actor, 200);
clutter_actor_restore_easing_state (actor);
[...]
clutter_actor_set_x (actor, 100);
and have the second set_x() update the easing in progress, instead of
being ignored.
https://bugzilla.gnome.org/show_bug.cgi?id=672945
|
|
|
|
|
| |
The test hasn't been updated after commit 229241b8, and was trying to
change the easing state without creating one.
|
| |
|
|
|
|
|
|
|
| |
We were using g_list_foreach() prior to the first Apocalypse, and that
function is resilient against changes to the list while iterating it;
since we are not using a GList any more, we need handle this case
ourselves.
|
|
|
|
|
| |
Devices that have touch valuator classes will be touchscreens or
touchpads; anything else should be ignored.
|
|
|
|
|
|
|
|
| |
This also avoids the warning
Cogl-WARNING **: ./cogl-buffer.c:215: GL error (1285): Out of memory
generated by cogl_buffer_map when the CoglBuffer has zero length.
|
| |
|
|
|
|
|
|
|
| |
clutter_text_buffer_set_text() expects a char count, not a byte
count, so pass -1 rather than using strlen.
https://bugzilla.gnome.org/show_bug.cgi?id=673783
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=672945
|
|
|
|
|
|
| |
A copy and paste thinko.
https://bugzilla.gnome.org/show_bug.cgi?id=672853
|
|
|
|
|
| |
The x_expand and y_expand members would mess up the initialization of
the constant LayoutInfo default structure.
|
|
|
|
|
|
| |
This patch fixes clutter to not crash when multiple animations share
the same timeline and the actors are explicitly destroyed before
the timeline completes (bug 672890)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The disjunction operator was misspelt as -O which tests whether the
following file is owned by the calling user. This doesn't take enough
arguments so bash was showing an error and the test was always
failing. This meant that NEED_XKB_UTILS was always false which should
have broken the build but the Makefile was mistakenly including
clutter-xkb-utils.c again if SUPPORT_WAYLAND is defined.
See 1b77565e for reference.
Reviewed-by: Emmanuele Bassi <ebassi@linux.intel.com>
(cherry picked from commit 04f2be34b2cba22acdb497feb5ecbcc3233ccc6a)
|
| |
|
| |
|
|
|
|
|
| |
Now that we have deprecation warnings and not full on symbol removal
from the headers, we can just skip Clutter's own, and use only GLib's.
|