Fabio:
I don't understand why applications that want to have a "transparent" backbuffer cannot just use display-tile. It is really simple to do, and target independent. Where is the need for saving the backbuffer inside the display target itself? Give even one real-world example of an application that cannot afford, for performance reasons, to run on display-tile, but at the same time cannot easily redraw (or draw the next frame.) You seem to be saying that there is demand for this feature, but I don't see any evidence of that at all. Also, you shouldn't use display-X as an example of a good GGI target. That target is pretty much a layered cake of hacks and kludges. I should know; I rewrote it. The backbuffer in that target is, as I have already said, there for the purpose of performance, not for "transparency." What you are advocating would be a *lot* of man hours, and, no, it's not that we are "lazy" as you have said, because noone that spends several hours of their spare time per week programming rather than playing video games, watching the tube, eating, sleeping, or having sex, all of which are generally much more fun, deserve to be called that. It's that we have a realistic grasp on the amount of work that we can afford to do per week, and the time it will take to reach our goals. -- Brian
