summaryrefslogtreecommitdiff
path: root/test/smoke-tests/frame-rate-tests/README
diff options
context:
space:
mode:
authorMatt Watson <mattdangerw@gmail.com>2013-09-05 17:11:06 -0700
committerMatt Watson <mattdangerw@gmail.com>2013-09-16 13:41:10 -0700
commit0dd5fa5fcec9bad9bd87ad0a9b04b63d47cd2a6c (patch)
treeae1b7c1fb7de77d19b487c5682e1cbf7acf6b913 /test/smoke-tests/frame-rate-tests/README
parent5424131d601b10d14d5e0293cc42677fe8bebb8e (diff)
Gtk and clutter tests for framerate
Not the greatest code, command line parsing could be better, but these are smoke tests. README with some instructions [endlessm/eos-sdk#299]
Diffstat (limited to 'test/smoke-tests/frame-rate-tests/README')
-rw-r--r--test/smoke-tests/frame-rate-tests/README16
1 files changed, 16 insertions, 0 deletions
diff --git a/test/smoke-tests/frame-rate-tests/README b/test/smoke-tests/frame-rate-tests/README
new file mode 100644
index 0000000..0c5aa17
--- /dev/null
+++ b/test/smoke-tests/frame-rate-tests/README
@@ -0,0 +1,16 @@
+Some basic animation tests to help see what kinds of animation are possible on
+what architectures.
+
+Usage:
+ CLUTTER_SHOW_FPS=1 gjs clutter.js [crossfade/slide] [1080/720]
+ GDK_DEBUG=frames gjs gtk.js [crossfade/slide] [1080/720]
+
+You can choose between a cross fade and a slide, and a 1080 or 720 image asset
+to animate. (The screen resolution and not the asset size should really
+determine frame rate, but just in case.)
+
+Clutter will print out a proper frame rate, whereas GTK will print out
+a series of intervals between draw updates. During an animation these
+should be at 16 milliseconds for 60 FPS.
+
+Click to trigger a slide. Press any key to quit.