It should only need to be a temporary workaround as I'll see if there is a better way to fix the original bug without impacting situations like this.
···
andrea.gavana@agip.it wrote:
Hello Robin & NG,
Yep, it was me. It was done to fix a bug reported in wxPython-dev about
the toolbar being sized incorrectly after tools were added/changed and
Realize was called again.Ok, I haven't seen the bug report, I should look closer to wxPython-dev
Try calling toolbar.SetBestFitting() size after you call
toolbar.Realize() to see if that makes a difference.It works! I have tested it with the new 2.6.2.1 release. Now I have just to
think if I have to let the user call SetBestFittingSize() in his code
(which is ugly, in my opinion) or let PyAUI take care of everything by
recognizing if the managed thing is a toolbar or not directly in the PyAUI
code. I'll try the second solution.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!