mutter

brl/mutter

History

Robert Bragg 0aacbd47b7 actor: make offscreen_redirect prop take flags + default off Because we have had several reports about significant performance regressions since we enabled offscreen redirection by default for handling correct opacity we are now turning this feature off by default. We feel that clutter should prioritize performance over correctness in this case. Correct opacity is still possible if required but the overhead of the numerous offscreen allocations as well as the cost of many render target switches per-frame seems too high relative the improvement in quality for many cases. On reviewing the offscreen_redirect property so we have a way to disable redirection by default we realized that it makes more sense for it to take a set of flags instead of an enum so we can potentially extend the number of things that might result in offscreen redirection. We removed the ability to say REDIRECT_ALWAYS_FOR_OPACITY, since it seems that implies you don't trust the implementation of an actor's has_overlaps() vfunc which doesn't seem right. The default value if actor::redirect_offscreen is now 0 which effectively means don't ever redirect the actor offscreen.		2011-08-30 16:20:16 +01:00
..
accessibility	a11y: Using proper way to register to window events	2011-08-23 17:22:17 +02:00
conform	actor: make offscreen_redirect prop take flags + default off	2011-08-30 16:20:16 +01:00
data	script: Rename "state" → "states"	2011-06-13 13:47:08 +01:00
interactive	build: Add -lm to the tests linker flags	2011-08-28 00:03:28 +01:00
micro-bench	build: Add -lm to the tests linker flags	2011-08-28 00:03:28 +01:00
performance	build: Add -lm to the tests linker flags	2011-08-28 00:03:28 +01:00
Makefile.am	tests: Add performance tracking framework	2011-07-04 17:27:48 +01:00
README	tests: Add performance tracking framework	2011-07-04 17:27:48 +01:00

README

Outline of test categories:

The conform/ tests should be non-interactive unit-tests that verify a single
feature is behaving as documented. See conform/ADDING_NEW_TESTS for more
details.

The performance/ tests are performance tests, both focused tests testing single
metrics and larger tests. These tests are used to report one or more
performance markers for the build of Clutter. Each performance marker is picked
up from the standard output of running the tests from strings having the form
"\n@ marker-name: 42.23" where 'marker-name' and '42.23' are the key/value pairs
of a single metric. Each test can provide multiple key/value pairs. Note that
if framerate is the feedback metric the test should forcibly enable FPS
debugging itself. The file test-common.h contains utility function helping to
do fps reporting.

The interactive/ tests are any tests whose status can not be determined without
a user looking at some visual output, or providing some manual input etc. This
covers most of the original Clutter tests. Ideally some of these tests will be
migrated into the conformance/ directory so they can be used in automated
nightly tests.

The accessibility/ tests are tests created to test the accessibility support of
clutter, testing some of the atk interfaces.

The data/ directory contains optional data (like images and ClutterScript
definitions) that can be referenced by a test.

Other notes:

• All tests should ideally include a detailed description in the source
explaining exactly what the test is for, how the test was designed to work,
and possibly a rationale for the approach taken for testing.

• When running tests under Valgrind, you should follow the instructions
available here:

        http://live.gnome.org/Valgrind

and also use the suppression file available inside the data/ directory.