Kouhei Sutou authored Apr 29, 2013 and Emmanuele Bassi committed Oct 07, 2014

It fixes DLL generation by cross compile.

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

Kouhei Sutou authored Apr 13, 2013 and Emmanuele Bassi committed Oct 07, 2014

It is installed under "clutter/win32/" directory. Other include paths
were fixed in 9da7dd19 but it was not
fixed.

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

We are disabling deprecation warnings in the build.

Such as the embed inside a GtkStack, as used in Cheese or Totem.

With help from Matthias Clasen (positioning inside the window), and
Jasper St. Pierre (Wayland API help).

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

Clicking on the "clickety" button in the gtk-clutter-test
will toggle, in a GtkStack, between a label, and a clutter-gtk
stage. It doesn't take very long to see the display artifacts after
that.

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

This reverts commit 0fc73a07.

I could have gotten away with this, if it wasn't for you meddling kids
and your Wayland.

Silences the compiler warning.

They have been long since deprecated by AM_CPPFLAGS and AM_CFLAGS.

The whole GtkClutterTexture class should be deprecated, and replaced by
a GtkClutterPixbuf class that implements the ClutterContent interface.

Don't use deprecated API, or disable deprecation warnings if that's not
possible without a more thorough investigation.

We *really* need to disable double buffering in GTK, otherwise we
flicker horribly.

We really need to drop the internal usage of ClutterX11TexturePixmap.

If Clutter has a GDK backend compiled in, we want to use that to
minimize the interaction surface between GTK and Clutter.

Calling clutter_actor_queue_redraw() triggers an asynchronous redraw
cycle, which triggers the callback from gtk-clutter-embed on the
'queue-redraw' signal, thus triggering another GTK+ paint cycle.

This ends up in a infinite draw loop.

This patch uses the clutter_stage_ensure_redraw() methods, which
prevents the 'queue-redraw' signal emission (this is exactly what we
want).

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

GtkClutterEmbed puts a filter on its GdkWindow to capture events and
pass them to the ClutterBackend. That works well for X11, because the
filter function receives an XEvent that can be directly fed to the
ClutterX11Backend.

For the GDK backend we can't do this because the filter function
provides an untranslated event to the callee. Thus we can't give a
valid GdkEvent to the ClutterGDKBackend.

To work around this problem the current GtkClutterEmbed listen to the
'event' signal of its widget, and puts fed them to the
ClutterGDKBackend.

The problem with this is that Gtk+ already does some filtering, mostly
on Expose events. This means that initially a GtkClutterEmbed often
appears unpainted with the Gdk backend of Clutter.

This patch adds the draw() vfunc on the widget and triggers a
clutter_actor_queue_redraw() upon call only for the GDK backend.

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

Using the gdk backend of Clutter, you could end up in situation where
none of the embedded widgets were being displayed. That's because the
conditions for invalidating the canvas where inconsistent with the
rest of the code.

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

Rob Bradford authored Sep 03, 2013 and Jasper St. Pierre committed Apr 16, 2014

The subsurface protocol lets us "embed" one surface within another. The
compositor will compose the two surfaces together to create a single
window. We use it here to take the surface we get from Clutter and make
that into a subsurface and then associate that subsurface with the main
surface coming from GTK+.

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

Bastien Nocera authored Mar 12, 2013 and Jasper St. Pierre committed Apr 16, 2014

Pretty useless, but gets the code running a little bit further.

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

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

Get these two methods back in sync.

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

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

This is what the post-parse hook does.

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

This is already done in the post-parse hook

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

This reverts commit cae45069.

We never installed the pick handler. If this is actually fixing
something with vfunc installed, we can re-revert this and add the
vfunc at the same time.

Instead of messing with the allocation leave it as is
and send the scaled size to clutter in the synthetic XConfigureEvent.

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

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