I've searched Google and this list but don't see any reference to this particular problem.
If I try to draw to the client area of a MDIParentFrame, it either doesn't repaint correctly or paints on top of a child, and moving the child around can erase the drawing until something occurs to redraw the parent, which is rare (minimizing and restoring will force it).
There's a wxPython-only test attached to the Dabo ticket for this at:
Try using the window returned from theMDIParent.GetClientWindow()
···
On 10/13/09 10:45 AM, Paul McNett wrote:
I've searched Google and this list but don't see any reference to this particular
problem.
If I try to draw to the client area of a MDIParentFrame, it either doesn't repaint
correctly or paints on top of a child, and moving the child around can erase the
drawing until something occurs to redraw the parent, which is rare (minimizing and
restoring will force it).
There's a wxPython-only test attached to the Dabo ticket for this at:
I've searched Google and this list but don't see any reference to this particular
problem.
If I try to draw to the client area of a MDIParentFrame, it either doesn't repaint
correctly or paints on top of a child, and moving the child around can erase the
drawing until something occurs to redraw the parent, which is rare (minimizing and
restoring will force it).
There's a wxPython-only test attached to the Dabo ticket for this at:
The test shows that a non-MDI situation will work as expected, but an MDI situation
will not.
The example uses a static bitmap but I've also tried drawing in the paint event with
similar if not identical results.
Try using the window returned from theMDIParent.GetClientWindow()
It works, at least in my simple test, although if I have a mdiChild.Show(), the StaticBitmap will appear both in the MDI Parent's client area as well as the MDI Child's client area.
Thanks, I'll play with this for awhile and see how it goes.