X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/623f5f70153c67b7ae860e87d657e42d821a2cf9..5c45e86bac1d3f0b08a452f6436481824f79fe5a:/src/msw/notebook.cpp diff --git a/src/msw/notebook.cpp b/src/msw/notebook.cpp index 7f4a3e3f17..432bcdda67 100644 --- a/src/msw/notebook.cpp +++ b/src/msw/notebook.cpp @@ -619,10 +619,11 @@ bool wxNotebook::InsertPage(size_t nPage, // succeeded: save the pointer to the page m_pages.Insert(pPage, nPage); - // for the first page (only) we need to adjust the size again because the - // notebook size changed: the tabs which hadn't been there before are now - // shown - if ( m_pages.GetCount() == 1 ) + // we may need to adjust the size again if the notebook size changed: + // normally this only happens for the first page we add (the tabs which + // hadn't been there before are now shown) but for a multiline notebook it + // can happen for any page at all as a new row could have been started + if ( m_pages.GetCount() == 1 || HasFlag(wxNB_MULTILINE) ) { AdjustPageSize(pPage); } @@ -698,6 +699,29 @@ void wxNotebook::OnSize(wxSizeEvent& event) rc.left = rc.top = 0; GetSize((int *)&rc.right, (int *)&rc.bottom); + // there seems to be a bug in the implementation of TabCtrl_AdjustRect(): it + // returns completely false values for multiline tab controls after the tabs + // are added but before getting the first WM_SIZE (off by ~50 pixels, see + // + // http://sf.net/tracker/index.php?func=detail&aid=645323&group_id=9863&atid=109863 + // + // and the only work around I could find was this ugly hack... without it + // simply toggling the "multiline" checkbox in the notebook sample resulted + // in a noticeable page displacement + if ( HasFlag(wxNB_MULTILINE) ) + { + // avoid an infinite recursion: we get another notification too! + static bool s_isInOnSize = false; + + if ( !s_isInOnSize ) + { + s_isInOnSize = true; + SendMessage(GetHwnd(), WM_SIZE, SIZE_RESTORED, + MAKELPARAM(rc.right, rc.bottom)); + s_isInOnSize = false; + } + } + TabCtrl_AdjustRect(m_hwnd, false, &rc); int width = rc.right - rc.left, @@ -918,14 +942,12 @@ wxColour wxNotebook::GetThemeBackgroundColour() // This is total guesswork. // See PlatformSDK\Include\Tmschema.h for values COLORREF themeColor; - wxUxThemeEngine::Get()->GetThemeColor - ( + wxUxThemeEngine::Get()->GetThemeColor( hTheme, 10 /* TABP_BODY */, 1 /* NORMAL */, - 3821, /* FILLCOLORHINT */ - & themeColor - ); + 3802 /* color of bg fill */, + &themeColor); wxColour colour(GetRValue(themeColor), GetGValue(themeColor), GetBValue(themeColor)); return colour; @@ -974,10 +996,11 @@ void wxNotebook::ApplyThemeBackground(wxWindow*, const wxColour&) #endif } +#if wxUSE_UXTHEME long wxNotebook::MSWWindowProc(WXUINT nMsg, WXWPARAM wParam, WXLPARAM lParam) { static bool g_TestedForTheme = false; - static bool g_UseTheme = false; + static bool g_supportsThemes = false; switch ( nMsg ) { case WM_ERASEBKGND: @@ -986,19 +1009,25 @@ long wxNotebook::MSWWindowProc(WXUINT nMsg, WXWPARAM wParam, WXLPARAM lParam) { int commCtrlVersion = wxTheApp->GetComCtl32Version() ; - g_UseTheme = (commCtrlVersion >= 600); + g_supportsThemes = (commCtrlVersion >= 600); g_TestedForTheme = true; } - // If using XP themes, it seems we can get away + // If currently an XP theme is active, it seems we can get away // with not drawing a background, which reduces flicker. - if (g_UseTheme) - return true; + if (g_supportsThemes) + { + wxUxThemeEngine *p = wxUxThemeEngine::Get(); + if (p && p->IsThemeActive() ) + { + return true; + } + } } } return wxControl::MSWWindowProc(nMsg, wParam, lParam); } - +#endif // #if wxUSE_UXTHEME #endif // wxUSE_NOTEBOOK