| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
We added symbols after 1.0, but we never added the per-version symbol
indices.
|
|
|
|
|
| |
We need an updated Docbook schema, as well as a couple of attributes, to
let gtk-doc generate a valid devhelp file.
|
| |
|
| |
|
|
|
|
| |
Allows GTK-Doc to find some symbols during distcheck.
|
|
|
|
| |
Silences a compiler warning.
|
|
|
|
| |
Silences various compiler warnings.
|
|
|
|
|
| |
The get_window_position_relative_to_parent() function has been moved
into Clutter's own backend.
|
| |
|
|
|
|
| |
Makes the UI a bit less awful.
|
|
|
|
|
|
|
| |
Ensure backward compatibility in case someone access the stage before we
map/show the embedding GtkWidget.
https://bugzilla.gnome.org/show_bug.cgi?id=755053
|
|
|
|
|
|
| |
This is mostly for the sake similarity.
https://bugzilla.gnome.org/show_bug.cgi?id=755017
|
|
|
|
|
|
|
|
|
| |
This changes works in conjunction with a Clutter change [1] to ensure
rendering is correctly synchronized at the different level of the stack.
[1] : https://git.gnome.org/browse/clutter/commit/?id=ee98a5bbe8ad21519d5e368ca5b2336e5d1da880
https://bugzilla.gnome.org/show_bug.cgi?id=755016
|
|
|
|
|
|
|
|
|
|
|
|
| |
Something I didn't quite realize is that the map vfunc is called :
"when widget is going to be mapped"
This is unnecessary now that we want to realize the stage only once
the embedding widget is actually visible. We just need to listen to
the "map-event" signal.
https://bugzilla.gnome.org/show_bug.cgi?id=754944
|
|
|
|
|
| |
Some of the gdk/wayland symbols we depend on are actually from Gtk+
3.8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On hide/unmap the GDK wayland backend might decide to destroy its
wayland surface [1]. There is no event notifying Clutter/Cogl of this.
We need to notify Clutter/Cogl that the surface has changed when the
embed widget becomes visible/invisible. So instead of mapping the
different mapped/visible/realized properties of the GtkWidget to the
ClutterStage, we take a different approach by considering that an
invisible GtkWidget means an unrealized ClutterStage.
[1] : https://git.gnome.org/browse/gtk+/commit/?id=87e2a7d4b23e633d0f2263d6ebd205c113eede0f
https://bugzilla.gnome.org/show_bug.cgi?id=754891
|
| |
|
| |
|
| |
|
|
|
|
| |
Use named icons instead.
|
|
|
|
|
|
| |
The way GtkStack manages its children is a bit peculiar. If we want to
avoid crashing inside Clutter because of a weird state, we need to
realize() the GtkClutterEmbed before getting the stage out of it.
|
|
|
|
|
| |
Deprecation warnings at run time are annoying, and it's not like stock
items add anything.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Instead of the old ones.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We should note that calling GTK API that deals with events from a
ClutterActor event handler will cause re-entrancy issues.
In other words:
If you call GTK event API
from Clutter event handlers
[ South Park ski instructor ]
You're going to have
a bad time
https://bugzilla.gnome.org/show_bug.cgi?id=745248
|
|
|
|
|
|
|
| |
Instead of relying on the widget one. This is similar to what we do when
running with the X11 backend.
https://bugzilla.gnome.org/show_bug.cgi?id=747489
|
|
|
|
|
|
| |
We need new API to get the GdkVisual.
https://bugzilla.gnome.org/show_bug.cgi?id=747489
|
| |
|
|
|
|
|
|
| |
It fixes DLL generation by cross compile.
https://bugzilla.gnome.org/show_bug.cgi?id=699202
|
|
|
|
|
|
|
|
| |
It is installed under "clutter/win32/" directory. Other include paths
were fixed in 9da7dd191dae7d1cc626ea22998145ebc2bb0722 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 0fc73a07770223964dbf41a20a4b0a8c3ef9a29c.
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.
|