mirror of
https://github.com/brl/mutter.git
synced 2024-11-13 01:36:10 -05:00
4258214e50
This test tried to do too much, and I can't remember the last time I saw this test work. It no longer tries to create a texture from an offscreen actor and it no longer tries to use shaders. It does though show that chaining of clutter_texture_new_from_actor now works, and that animating the source actor is reflected in textures created from it. When run you should see three actors: - on the left is the pristine source actor rotating around the y-axis - in the middle is the first texture created from the source actor - and on the right a texture created from the middle actor Note: the somewhat strange bobbing of the middle and right textures is actually correct given how it was decided long ago to map the transformed (to screen space) allocation of the source actor to the texture. When the hand spins around the perspective projection of the top of the hand results in the origin of the texture bobbing up to a higher stage position, but the position of the textures is fixed. This design also means we end up reallocating our offscreen draw buffer every frame that the actors transformed size changes, which isn't ideal. |
||
|---|---|---|
| .. | ||
| conform | ||
| data | ||
| interactive | ||
| micro-bench | ||
| tools | ||
| .gitignore | ||
| Makefile.am | ||
| 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 approach taken for testing.