No, I tried that. It is not my own control who is earsing itself in the paint method. It is the parent control who does. I cant do the double buffering, because I dont have access to the parent control surface. In fact, I think I started this thread for my own ignorance (I saw what I think now could possibly be a bug:
The 0x20 style was actually the answer to my question - though not the solution to my problem. If the parent paints in its onpaint event, it does exactly what I what it to do. In my case, though, DirectX handles the painting and my app never knows about it. I guess Ill have to keep digging on how to use DirectShows Overlay Mixer from C#, but that should go in the DirectX section.
If any of you have done that/have any ide about how to do it, please let me know! (wrappers, code, etc). If not - it is not urgent now, ill keep exploring, and Ill post here if and when I solve it.
Thanks for the help. I learned a lot in this thread.
and I was trying to reproduce it as it was nearly the desired effect)When I hide the window (not minimize, not covering with another window, but moving the control off-screen and then moving it back in quickly), I get the desired effect on some random regions of the control. On the rest of the control, I either get the same black or grey background, or the form background, whatever is behind the form (usually a piece of the VS.NET IDE).
The 0x20 style was actually the answer to my question - though not the solution to my problem. If the parent paints in its onpaint event, it does exactly what I what it to do. In my case, though, DirectX handles the painting and my app never knows about it. I guess Ill have to keep digging on how to use DirectShows Overlay Mixer from C#, but that should go in the DirectX section.
If any of you have done that/have any ide about how to do it, please let me know! (wrappers, code, etc). If not - it is not urgent now, ill keep exploring, and Ill post here if and when I solve it.
Thanks for the help. I learned a lot in this thread.