[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-dev] invalidated bounds debugging
From: |
strk |
Subject: |
[Gnash-dev] invalidated bounds debugging |
Date: |
Fri, 8 Dec 2006 14:25:10 +0100 |
I'm ready to add invalidated bounds testing to our
testsuite, but it seems I can't handle to understand the
mechanism of it.
What I would expect is that:
0) get_invalidated_bounds is misnamed, should be
expand_to_invalidated_bounds() as it actually
expands the given rect to enclose the invalidated bounds.
1) Before *any* ::advance() is called, the
get_invalidated_bounds() should add NOTHING
to the provided bounds.
2) After *first* call to advance(), the get_invalidated_bounds()
should turn the bounds into the WORLD bounds (everything changed)
3) From *second* call on, the get_invalidated_bounds() should
only add the boundaries of things that actually changed
since when ? Last call to ::display ? Last call to
get_invalidated_bounds () ??
--strk;
- [Gnash-dev] invalidated bounds debugging,
strk <=