[wxMac 2.8x] wxWindow::DoGetBestSize bug still not solved
Robin Dunn
robin at alldunn.com
Fri Apr 13 16:37:43 PDT 2007
Vadim Zeitlin wrote:
> On Sat, 14 Apr 2007 00:29:43 +0200 H <H at h.com> wrote:
>
> H> > Which window's best size is the problem for you? The tree? The
> H> > treebook? Each of these have their own DoGetBestSize method.
> H>
> H> The tree's window is the problem. You can see the bug when running the
> H> notebook sample. Choose the treebook and you will see that the tree's
> H> window is not correctly sized. The root of the bug is
> H> wxWindow::DoGetBestSize returning (0, 0) instead of taking the
> H> scrollbars into account when initializing/determining the initial size
> H> of the tree's window.
> H> By changing the size of the frame the problem will disappear.
>
> I still don't understand why does the window have scrollbars in the first
> place if it's empty. And if it's not empty, why does it have (0,0) best
> size? I.e. there is probably a deeper reason for this bug.
>
> OTOH I'd agree that DoGetBestSize() should account for the scrollbars if
> they happen to be shown. But then it should do it under all platforms, of
> course...
I seem to recall that there is code somewhere that adjusts best size by
the difference between client size and actual size, so if the
wxWindowMac does client size properly when the scrollbars are shown then
it should work.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
More information about the wx-users
mailing list