mutter/examples
Gustavo Noronha Silva 0c75e17814 Add PanAxis mode that automatically pins scroll based on initial movement
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
2015-06-11 15:47:48 -03:00
..
basic-actor.c examples/basic: Use the event type and not a flag 2012-07-30 10:54:18 +01:00
bin-layout.c Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
box-layout.c examples/box: Allow toggling animations 2012-08-20 17:58:30 +01:00
canvas.c examples/canvas: Resize the canvas on allocation changes 2012-05-11 17:38:53 +01:00
constraints.c examples/constraints: Do not use deprecated API 2012-06-06 13:37:02 +01:00
drag-action.c examples: Update drag and drop action code 2012-05-24 13:58:31 +01:00
drop-action.c examples: Remove a stray restore_easing_state() 2013-06-15 12:12:43 +01:00
easing-modes.c examples/easing-modes: Use newly added modes 2012-07-19 22:13:28 -04:00
flow-layout.c flow-layout: Add :snap-to-grid property 2013-05-11 10:54:38 -04:00
grid-layout.c Remove usage of ClutterLayoutManager easing API 2012-07-11 13:22:21 +01:00
image-content.c Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
layout-manager.c Stop using macros for accessing actor state 2015-04-23 17:39:30 +01:00
Makefile.am build: Use libtool macros to find libm 2015-03-03 17:23:37 +00:00
pan-action.c Add PanAxis mode that automatically pins scroll based on initial movement 2015-06-11 15:47:48 -03:00
README
redhand.png Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
rounded-rectangle.c examples: Add transparency to the rounded rectangle 2015-04-30 13:04:32 +01:00
scroll-actor.c Move scroll actor test to the examples 2012-05-17 10:57:15 +01:00
threads.c examples: Use pivot point, not anchor point 2012-07-11 13:22:20 +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.