mutter/examples
Emmanuele Bassi de4d70af69 timeline: Add a new "stopped" signal
The ::stopped signal is emitted when the timeline has been completely
exhausted or when the timeline has been programmatically stopped by
using clutter_timeline_stop(); the notification at the end of the
timeline run allows to write handlers without having to check whether
the current repeat is the last one, like we are forced to do when using
the ::completed signal.

Based on the patch by: Jasper St. Pierre <jstpierre@mecheye.net>

https://bugzilla.gnome.org/show_bug.cgi?id=676854
2012-05-31 09:54:23 +01:00
..
basic-actor.c timeline: Add a new "stopped" signal 2012-05-31 09:54:23 +01:00
bin-layout.c Move examples from tests/interactive to a new top-level 2012-05-01 19:00:35 +01:00
canvas.c examples/canvas: Resize the canvas on allocation changes 2012-05-11 17:38:53 +01:00
constraints.c Move examples from tests/interactive to a new top-level 2012-05-01 19:00:35 +01:00
drag-action.c examples: Update drag and drop action code 2012-05-24 13:58:31 +01:00
drop-action.c examples: Update drag and drop action code 2012-05-24 13:58:31 +01:00
easing-modes.c Move the easing modes test into the examples 2012-05-02 18:37:36 +01:00
flow-layout.c examples: Allow optional animations in flow-layout 2012-05-30 12:47:21 +02:00
image-content.c Move examples from tests/interactive to a new top-level 2012-05-01 19:00:35 +01:00
layout-manager.c examples: Update layout-manager example to use the animations API 2012-05-28 19:37:19 +02:00
Makefile.am Move scroll actor test to the examples 2012-05-17 10:57:15 +01:00
README Move examples from tests/interactive to a new top-level 2012-05-01 19:00:35 +01:00
rounded-rectangle.c Add rounded corners rectangle example using Canvas 2012-05-04 17:54:51 +01:00
scroll-actor.c Move scroll actor test to the examples 2012-05-17 10:57:15 +01:00
threads.c Move examples from tests/interactive to a new top-level 2012-05-01 19:00:35 +01:00

The code in this directory is meant to be XIncluded into the Clutter API
reference, and thus is to be considered part of the Clutter documentation.

As such, the code MUST be:

  - correct;
  - idiomatic, i.e. show how a task is meant to be achieved using the
    best possible practices given the current API;
  - well documented;
  - ready for copy and paste.