That answer seems to imply that on Windows at least, the content is double-buffered, including that rendered by plugins. Or did I misinterpret your answer?
Well.. my answer was deliberately vague as to handling of plugins on Windows, because I simply don't know whether that ends up double-buffered or not for non-windowless plugins.
If it's double buffered then I'm presuming everything is rendered into some sort of offscreen bitmap or drawing context which is then blitted to the screen. In which case it ought to be relatively easy to hook to the window update code and do something else with the buffer, instead of (or as well as) blitting it to the window.
True. People who ask about rendering to memory usually want to do so without actually showing any windows on screen (and possibly without the ability to show such windows, eg a Unix box with no X server running). Which is a little more involved than what it sounds like you need.
For our purposes we could probably hack things so that they are always in windowless mode, as long as the plugin supports it. I'm new to all this so I don't know - is it likely that most of the mainstream plugins will support it?
The problem is that the plugin is what decides whether it's in windowless mode or not (and renders differently based on that). At least that's my understanding of the situation.
That said, Flash and Java support windowless mode last I checked. Don't know about others.
Would you have any idea who I could talk to about that floating code, or where I could find it?
[EMAIL PROTECTED] is the author; he probably has it sitting about somewhere.
-Boris _______________________________________________ mozilla-embedding mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-embedding
