| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The `install` argument for configure_file() is not needed if set to a
`true` constant value while passing `install_dir`.
|
|\
| |
| |
| |
| | |
docs: Add missing settings.ini Environment group keys
See merge request GNOME/clutter!8
|
| |
| |
| |
| |
| | |
Backends, Drivers and SyncToVblank are available but not documented in
"Running Clutter".
|
|/
|
|
|
|
|
|
|
| |
GNU libtool is documented to support -export-dynamic and GNU ld is
documented to support --export-dynamic. However, GCC isn't documented
to support them. While GCC does support -export-dynamic for backwards
compatibility, Clang doesn't support it and interprets it wrongly. This
causes warnings to be shown during linking because Clang splits it into
'-e xport-dynamic' and the linker can't find 'xport-dynamic' symbol.
|
|
|
|
| |
That's where GitLab expects it.
|
|
|
|
|
| |
The color variables in some cookbook examples are unused, and the
compiler is complaining.
|
|
|
|
|
| |
We're missing the CLUTTER_SCROLL_SMOOTH case in the switch over the
scroll direction, and the compiler complains about it.
|
|
|
|
|
| |
We must build the examples and install their sources with the Meson
build as well as the Autotools one.
|
|
|
|
| |
Fix distcheck with the Autotools build.
|
|
|
|
| |
The gtk-doc entities are in lower case, not upper case.
|
|
|
|
|
| |
The various documentation files are already in formatted in a
Markdown-like fashion, so let's make it official.
|
|
|
|
|
|
|
|
|
|
|
| |
Both the API reference and the Cookbook.
This requires a little bit of surgery on the Autotools build as well,
namely that we need to stop generating the main gtk-doc XML file from
a template at configuration time; we should, instead, generate and
include a gtkdocentities.ent file both for the Meson build (where we
generate the file ourselves) and for the Autotools build (where
gtk-doc.make does it for us).
|
|
|
|
|
|
| |
We split them for some reasons under the common and cookbook
directories, but it's completely pointless: the XSLT and CSS style
sheets are only used by the cookbook.
|
|
|
|
|
|
|
| |
Having a 'build' directory makes is a bit awkward for tools packaging
Clutter, and the rapidly coalescing consensus on the GNOME platform,
pushed by the port to Meson, is to call the directory for ancillary
build files 'build-aux'.
|
|
|
|
|
| |
Even if Clutter is an old project, it does not mean it shouldn't receive
some build system love.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Those can be used to implement different scrolling behaviors.
The fields have been added to ClutterScrollEvent itself. According
to pahole, this makes the struct as big as ClutterButtonEvent and
ClutterTouchEvent, so already at the limit of the ClutterEvent
union.
https://bugzilla.gnome.org/show_bug.cgi?id=757026
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have an hardcoded list of drivers we have to go through when creating
a Cogl context. Some platforms may expose those drivers, but not be the
preferred ones.
In order to allow users and system integrators to override the list of
drivers, we should crib the same approach used by GDK, and have an
environment variable with a list of drivers to try.
The new environment variable is called `CLUTTER_DRIVER` and accepts a
comma-separated list of driver names, which will be tested in sequence
until one succeeds. There's also an additional '*' token which is used
to ask Clutter to fall back to the internally defined preferred list of
drivers.
https://bugzilla.gnome.org/show_bug.cgi?id=742678
|
|
|
|
|
| |
We need an updated Docbook schema, and a couple of other attributes, so
that gtk-doc will generate a valid devhelp file.
|
| |
|
|
|
|
| |
These are needed in order to make these events binding friendly
|
|
|
|
|
|
|
|
|
| |
We now have ClutterTouchpadPinchEvent and ClutterTouchpadSwipeEvent,
each bringing the necessary info for the specific gesture. Each
of these events is defined by begin/update/end/cancel phases.
These events have been also made to propagate down/up the pointer
position, just like scroll and button events do.
|
|
|
|
|
|
|
|
|
|
| |
When binding models to actors to map items to children we don't often
need the full control of a function; in many cases we just need to
specify the type of the child we want to construct and the properties
on both the item and the child that we want to bind.
We should provide a simple convenience function that does all this for
us.
|
|
|
|
|
|
|
|
|
|
| |
It can be useful to bind the children list to set of objects inside a
GListModel implementation; the GListModel stores the objects, and every
time the model changes, a function is called that maps each object in
the model to a newly created ClutterActor, which is then added as a
child. This API, along with the property binding one inside GObject,
allows automatic creation of views based on object models that update
themselves without manual intervention.
|
|
|
|
|
|
|
| |
This code is inspired by the implementation of the same feature for the
Mx toolkit's MxKineticScrollView. See commit 4d08771.
https://bugzilla.gnome.org/show_bug.cgi?id=707982
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Straight from Cogl.
This allows us to propagate the GdkVisual Cogl and Clutter use to
embedding toolkits, like GTK+.
The function is annotated as being added to the 1.22 development
cycle because it will be backported to the stable branch, so that
downstream developers can package up a version of Clutter that does
not crash on nVidia.
https://bugzilla.gnome.org/show_bug.cgi?id=747489
|
|
|
|
|
| |
Since we only have one API reference, we can drop the clutter/
sub-level, and have all the files under doc/reference.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's pretty much pointless to have two API references:
• the Cally API reference is fairly small
• the build system is already complicated as it is
• GTK-Doc isn't smart enough to ignore sub-directories
• Cally is not a separate library, just a separate namespace
There are some issues with GTK-Doc not accepting multiple namespaces,
but nothing seriously tragic.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We don't use deprecation guards any more, in favour of compiler
annotations and gtk-doc annotations.
|
|
|
|
|
| |
This should catch missing symbols during `make check`, and hopefully
lead to their addition prior to a release.
|
|
|
|
|
| |
If we don't specify the files, gtk-doc won't find the symbols even if
they are documented.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nobody has been compiling Clutter with profiling enabled in a long time.
UProf itself hasn't been updated in 5 years, and it still depends on
deprecated components like dbus-glib, with no port to GDBus in sight.
The profiling code was moderately useful in the past, but these days
it's probably better to profile Cogl than Clutter itself; timing
information can be extracted by the timestamp on each diagnostic message
that is now available by default in the CLUTTER_NOTE macro, and we can
add ad hoc counters where needed.
|
|
|
|
|
| |
Instead of using `-lm` everywhere, use LT_LIB_M inside configure.ac, and
$(LIBM) inside Makefile.am.
|
| |
|
| |
|
| |
|
|
|
|
| |
Otherwise gtk-doc won't be able to find some generated files.
|
|
|
|
|
|
|
|
|
|
| |
Toolkits may need to paint actors internally outside the normal tree
(for example to create a shadow shape), in which case they need to
control the opacity directly.
https://bugzilla.gnome.org/show_bug.cgi?id=677412
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
| |
|
|
|
|
|
|
| |
This may be useful when trying to identify the device across sessions.
https://bugzilla.gnome.org/show_bug.cgi?id=740759
|
| |
|