Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Patches to compile and link C::B against wxWidgets 2.8.0
stahta01:
#if !WXWIN_COMPATIBILITY_2_4
#define wxHIDE_READONLY 0
#endif
This implies that wxHIDE_READONLY is 0 when WXWIN_COMPATIBILITY_2_4 is 0.
And, the code above ONLY makes sense when WXWIN_COMPATIBILITY_2_4 is 0; otherwise the code is not needed. So, are you testing with WXWIN_COMPATIBILITY_2_4 = 1 or = 0?
Tim S
afb:
--- Quote from: stahta01 on November 24, 2006, 06:31:30 pm ---And, the code above ONLY makes sense when WXWIN_COMPATIBILITY_2_4 is 0; otherwise the code is not needed.
--- End quote ---
Right, I was only using it in the wxWidgets 2.8 builds. What I meant was that I didn't change the 2.4 compat.
--- Quote ---So, are you testing with WXWIN_COMPATIBILITY_2_4 = 1 or = 0?
--- End quote ---
On for 2.6, Off for 2.8. This was just discussing your patch, but it's interesting that you mention that using wxWidgets 2.6 with WXWIN_COMPATIBILITY_2_4=0 is also unstable (I knew that wxWidgets 2.8 was, but...) Guess I need to build another debugging version of wx26 then, with the 2.4 compat disabled.
stahta01:
--- Quote from: afb on November 25, 2006, 11:09:01 am ---On for 2.6, Off for 2.8. This was just discussing your patch, but it's interesting that you mention that using wxWidgets 2.6 with WXWIN_COMPATIBILITY_2_4=0 is also unstable (I knew that wxWidgets 2.8 was, but...) Guess I need to build another debugging version of wx26 then, with the 2.4 compat disabled.
--- End quote ---
Yes, wxWidgets 2.8 with WXWIN_COMPATIBILITY_2_4=1, works much better than with WXWIN_COMPATIBILITY_2_4=0.
I am going to work on this issue using wxWidgets 2.6 with WXWIN_COMPATIBILITY_2_4=0 in order to remove the whole set of wxWidgets 2.8 changes from the picture.
Do you think I should start a new thread on wxWidgets 2.6 with WXWIN_COMPATIBILITY_2_4=0 issues?
Tim S
afb:
--- Quote from: stahta01 on November 26, 2006, 02:06:01 am ---I am going to work on this issue using wxWidgets 2.6 with WXWIN_COMPATIBILITY_2_4=0 in order to remove the whole set of wxWidgets 2.8 changes from the picture.
Do you think I should start a new thread on wxWidgets 2.6 with WXWIN_COMPATIBILITY_2_4=0 issues?
--- End quote ---
Sounds like a good plan, and it should probably go in a separate thread.
(Building a wxMac 2.6 with --enable-debug --disable-compat24 now...)
afb:
You were right, it seems that the crashes with wxWidgets 2.8.0 are in fact general crashes when compat24 is turned off... I'm seeing the same ones in wxWidgets 2.6.3p2 now, that I did with wxWidgets 2.8.0rc1 earlier:
Settings > Environments *crash*
--- Code: ---../src/generic/listctrl.cpp(3699): assert "wxAssertFailure" failed: invalid item index in SetItem
--- End code ---
Settings > Editor *crash*
--- Code: ---../src/generic/listctrl.cpp(3699): assert "wxAssertFailure" failed: invalid item index in SetItem
--- End code ---
Settings > Compiler and Debugger *crash*
--- Code: ---../src/common/list.cpp(326): assert "wxAssertFailure" failed: invalid index in wxListBase::Item
--- End code ---
Settings > Global variables *crash*
--- Code: ---../src/mac/carbon/choice.cpp(217): assert "wxAssertFailure" failed: wxChoice::GetString(): invalid index
--- End code ---
So it seems that debugging/fixing Code::Blocks with this compat setting turned off in wxWidgets 2.6 is a good idea to start with, as it is both good now and will also help running with wxWidgets 2.8 later ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version