mutter

brl/mutter

History

Neil Roberts 9c5663d671 [timeline] Don't clamp the elapsed time when a looping tl reaches the end

The new-frame signal of a timeline was previously guaranteed to be
emitted with the elapsed_time set to the end before it emits the
completed signal. This doesn't necessarily make sense for looping
timelines because it would cause the elapsed time to be clamped to a
slightly off value whenever the timeline restarts. This patch makes it
perform the wrap around before emitting the new-frame signal so that
the elapsed time always corresponds to the time elapsed since the
timeline was started.

Additionally it no longer fudges the msecs_delta property to make the
marker check work so clutter_timeline_get_delta will always return the
wall clock time since the last frame.

2009-06-10 17:47:33 +01:00

conform

[timeline] Don't clamp the elapsed time when a looping tl reaches the end

2009-06-10 17:47:33 +01:00

data

…

interactive

[stage] Rename fullscreen methods

2009-06-09 14:07:35 +01:00

micro-bench

Limit the frame rate when not syncing to VBLANK

2009-06-09 15:03:56 +01:00

tools

[tests/tools] Don't install libdisable-npots.so

2009-02-24 17:04:05 +00:00

.gitignore

[gitignore] Ignore two newly introduced tests

2009-03-25 20:58:22 +00:00

Makefile.am

…

README

…

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 micro-bench/ tests should be focused perfomance test, ideally testing a single metric. Please never forget that these tests are synthetec and if you are using them then you understand what metric is being tested. They probably don't reflect any real world application loads and the intention is that you use these tests once you have already determined the crux of your problem and need focused feedback that your changes are indeed improving matters. There is no exit status requirements for these tests, but they should give clear feedback as to their performance. If the framerate is the feedback metric, then the test should forcibly enable FPS debugging.

The interactive/ tests are any tests whos 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.

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 aproach taken for testing.