Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Will patches to compile and link C::B against wxWidgets 2.7.1 be accepted?

<< < (15/18) > >>

David Perfors:
Beside that, we have to wait for the thirdparty libs (wxScintilla amd wxPropGrid) to support the new version. That is nicer than patching those libs ourself.

stahta01:
The only thing I can find that requires WXWIN_COMPATIBILITY_2_4 to be 1 seems to be the use of wxHIDE_READONLY. So, when we are ready to move to support for wxWidgets 2.8 we need to decide how to handle wxHIDE_READONLY. I see two ways remove them or place then in #if wxCHECK_VERSION blocks.

Note: A third way I used as testing work around was to -DwxHIDE_READONLY=0 with WXWIN_COMPATIBILITY_2_4 set to 0 in setup.h.

I also looked up the deprecated methods messages on compiling C::B (did not look at contrib messages yet.)

2.4 deprecated methods with Good Methods under 2.6 per chm and headers
  ::wxStartTimer                       // This is deprecated use wxStopWatch::Start instead
  ::wxGetElapsedTime                // This is deprecated use wxStopWatch::Time instead
  wxDC::BeginDrawing                // This is deprecated and does nothing. Don't use.
  wxDC::EndDrawing                  // This is deprecated and does nothing. Don't use.
  ::wxGetWorkingDirectory          // See ::wxGetCwd as a replacement

2.6 deprecated methods with New Methods under 2.7 per chm and headers
  wxWindow::SetBestFittingSize    // See SetInitialSize(size) as a replacement
  wxWindow::GetBestFittingSize    // See GetEffectiveMinSize() as a replacement
  wxRect::Inside                        // See wxRect::Contains as a replacement
  wxAuiManager::SetFrame          // See wxAuiManager::SetManagedWindow as a replacement

deprecated methods with questions about how to fix or if they need fixing
  wxPathList::Member                 // May or may NOT be deprecated; conflicting code and docs
  __comp_ctor wxFontDialog::wxFontDialog see include/wx/msw/fontdlg.h:42


Tim S

afb:

--- Quote from: stahta01 on November 08, 2006, 08:53:58 am ---Note: A third way I used as testing work around was to -DwxHIDE_READONLY=0 with WXWIN_COMPATIBILITY_2_4 set to 0 in setup.h.
--- End quote ---

I did this too, but stuck it in the header.


--- Code: ---#if !WXWIN_COMPATIBILITY_2_4
#define wxHIDE_READONLY 0
#endif

--- End code ---

afb:

--- Quote from: sethjackson on November 08, 2006, 12:33:52 am ---wxAUI is now part of wx so we shouldn't need it (in the C::B sources) anymore if (and presumeably when) C::B switches to either 2.7 or 2.8.
--- End quote ---

Please see the AUI patch, there is no currently need to choose -
you can have same CB code link with both wx 2.6 and wx 2.8 ?

http://developer.berlios.de/patch/?func=detailpatch&patch_id=1630&group_id=5358

rjmyst3:

--- Quote from: mispunt on November 08, 2006, 07:43:58 am ---Beside that, we have to wait for the thirdparty libs (wxScintilla amd wxPropGrid) to support the new version. That is nicer than patching those libs ourself.

--- End quote ---

wxPropGrid and wxScintilla already support wxWidgets2.7 - we use them in wxFormBuilder, which is built with wxWidgets2.7.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version