No updates after .Freeze()/.Thaw() ?

Robin Dunn wrote:

This only refreshes the frame, not it's children. Try calling self.btn2.Refresh() instead.

Yes, you're right, this helps with the button, but if I replace
the button with ListCtrl and do .Refresh() on it, it's still not redrawn correctly.
In the real app I have a panel with a bunch of dynamically created
controls. I've tried recursively calling Refresh() on all its
children after the .Thaw(), but ListCtrls still do not look right. I forgot to mention this, but what bothers me is that the code worked
perfectly under 2.4, without the need to call any .Refresh().
Something seems to have changed here in 2.5. Probably I've missed
something in the 2.4 - 2.5 migration?
When compiling from CVS I've peeked at the .Thaw() implementation,
and it seems that it's supposed to do a redraw without any
additional efforts.

Regards,
Ury Marshak

Ury Marshak wrote:

Robin Dunn wrote:

This only refreshes the frame, not it's children. Try calling self.btn2.Refresh() instead.

Yes, you're right, this helps with the button, but if I replace
the button with ListCtrl and do .Refresh() on it, it's still not redrawn correctly.
In the real app I have a panel with a bunch of dynamically created
controls. I've tried recursively calling Refresh() on all its
children after the .Thaw(), but ListCtrls still do not look right. I forgot to mention this, but what bothers me is that the code worked
perfectly under 2.4, without the need to call any .Refresh().
Something seems to have changed here in 2.5. Probably I've missed
something in the 2.4 - 2.5 migration?
When compiling from CVS I've peeked at the .Thaw() implementation,
and it seems that it's supposed to do a redraw without any
additional efforts.

Please create a bug report about this with a category of "wxMSW Specific"

ยทยทยท

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!