Closed by Nicolas Pennequin (nicolas_p)
Thursday, 03 July 2008, 15:37 GMT Reason for closing: Wont FixAdditional comments about closing: This is a limitation of how WPS
rendering is done. It's easy to
work around it.

I just confirmed this with a clean CVS build simulator and the provided test-case (although for some reason neither the clock nor the background image worked in the simulator, the bug was very much visible).

The tracker should _never_ be used to report "bugs" against inofficial builds unless the reporter states that this behaviour is also present in the official build (and he can reproduce it with a current cvs build!) in the first place. The tracker gets abused for support requests and similar pretty much recently which clutters it and degrades its usability. Thus I find it unacceptable to report against inofficial builds.

I have a solution for the problem.
The test WPS clearly shows the problem is solved (although the text under the picture doesn't reappear instantly), and other WPSs don't seem to be broken.
I might commit the patch but it needs to be cleaned up a bit first and the issue discussed.

I never committed the patch above because it became outdated and felt a bit clumsy anyway.
I've committed something that aims to fix similar problems, but doesn't quite fix this one.

A solution is to make the disappearing text lines dynamic by adding %?mh<> conditionals in each of them. I know it's a bit hackish, but I prefer having a hack in a WPS than in the displaying code.

The more general issue is very similar to FS#6827: static vs. dynamic. Dynamic things will always overwrite static things. To avoid this, there are several solutions, including forcing the static elements to become dynamic.
However, the best solution is to avoid overlapping, as the WPS code wasn't meant for it anyway.

I don't think viewports have solved the issue, but I'm tempted to close this as "Not a Bug". It's more of a limitation of the WPS displaying code. I think allowing overlap would require a complete restructuring of the displaying code and frankly it's not on my priority list.