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.

Carlos Garnacho authored Jun 25, 2014 and Emmanuele Bassi committed Aug 13, 2014

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
(cherry picked from commit 02590f08

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Carlos Garnacho authored Jul 08, 2014 and Emmanuele Bassi committed Aug 13, 2014

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
(cherry picked from commit 8d669ab8

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Carlos Garnacho authored Jul 11, 2014 and Emmanuele Bassi committed Aug 13, 2014

Input devices must get the proper button state, in addition to keyboard
modifiers.

https://bugzilla.gnome.org/show_bug.cgi?id=733062
(cherry picked from commit f6fd0297

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Giovanni Campagna authored Jul 17, 2014 and Emmanuele Bassi committed Aug 13, 2014

We need to unref the timeline

https://bugzilla.gnome.org/show_bug.cgi?id=733300
(cherry picked from commit c167d3a4

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Carlos Garnacho authored Jul 21, 2014 and Emmanuele Bassi committed Aug 13, 2014

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
(cherry picked from commit 0c0c069b

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Tom Beckmann authored Jul 19, 2014 and Emmanuele Bassi committed Aug 13, 2014

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

We don't want tests to fail for deprecation messages; we already disable
deprecation warnings from the compiler for the same reason.

(cherry picked from commit 9c9b37cb

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Carlos Garnacho authored Jun 25, 2014 and Emmanuele Bassi committed Jun 26, 2014

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
(cherry picked from commit 4c4e72a9

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Carlos Garnacho authored Jun 25, 2014 and Emmanuele Bassi committed Jun 26, 2014

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
(cherry picked from commit 42f6828c

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Don't use direct struct access.

(cherry picked from commit 036c2b37

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

Carlos Garnacho authored Jun 25, 2014 and Emmanuele Bassi committed Jun 26, 2014

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
(cherry picked from commit 02590f08

)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

The 'state' field should be used for pointer events without button
information. Pointer events that have button information should use
the 'button' field.

https://bugzilla.gnome.org/show_bug.cgi?id=732143

Currently, due to the way that Visual Studio 2010+ projects are handled,
the "install" project does not re-build upon changes to the sources, as it
does not believe that its dependencies have changed, although the changed
sources are automatically recompiled.  This means that if a part or more
of the solution does not build, or if the sources need some other fixes
or enhancements, the up-to-date build is not copied automatically, which
can be misleading.

Improve on the situation by forcing the "install" project to trigger its
rebuild, so that the updated binaries can be copied.  This does trigger an
MSBuild warning, but having that warning is way better than not having an
up-to-date build, especially during testing and development.

The coordinates translated by the XI2 device manager were being clamped using
the X window size kept by StageX11. However, when the stage is fullscreen,
that size is not updated to the screen size, but kept the same in order to
allow going back to it when the stage goes out of fullscreen.

https://bugzilla.gnome.org/show_bug.cgi?id=731268

And get CLUTTER_EVENT_LEAVE out of the touch event compression logic, as
touches are always implicitly grabbed. If no sequence check is done, only
the last touch update would be emitted, even if multiple sequences got
updated.

https://bugzilla.gnome.org/show_bug.cgi?id=730577

When an actor carrying canvas content is repainted, it will currently reupload
the data from the buffer to a texture. While this is not a performance problem
on a desktop, some mobile environments take a big performance hit. This
change tracks data changes and only recreates the texture if necessary.

https://bugzilla.gnome.org/show_bug.cgi?id=729144

Using GdkPixbuf, which is what we expect people to use anyway.

Gustavo Noronha Silva authored Apr 18, 2014 and Gustavo Noronha Silva committed Apr 18, 2014

By creating and starting the timer on clutter_main() an assumption is made
that that is how the main loop will be run for all clutter applications.
With more and more applications moving to GApplication, this assumption no
longer holds true.

Moving to clutter_init() means we are starting the timer earlier than we
should, and by not stopping it when the main loop quits we are taking a
measure that is later than we should. I believe it is safe to consider
those are close enough to the actual beginning and quitting of the main
loop in practice.

https://bugzilla.gnome.org/show_bug.cgi?id=728521

Cogl, when built with the SDL winsys, will include the SDL headers when
Cogl-based programs are built, which causes the SDL's wrapper for main()
to be used on Windows, causing an implicit requirement that all Cogl-based
apps must link to SDL2.lib and SDL2main.lib.  Avoid this behavior by
defining SDL_MAIN_HANDLED in the CFLAGS of the sample and interactive test
programs

Use the difference between the elapsed time and the available budget, so
that the message can be read more easily.

https://bugzilla.gnome.org/show_bug.cgi?id=728177

Instead of just bailing out when initializing the test suite, we can do
a much better job and skip all the tests. This means that the TAP driver
will work correctly instead of dying a horrible death, and we get a nice
report with a proper cause of the test skipping.

The Visual Studio build files have been updated to not use it, so we can
remove it from the repository.