Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

removed the note about wxEvent::Clone() startup test as it was removed

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@60181 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2009-04-15 21:14:25 +00:00
parent 4262848117
commit 975fe60bba
1 changed files with 0 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/changes.txt
View File

@@ -226,11 +226,6 @@ Changes in behaviour which may result in compilation errors
- wxEVT_GRID_CELL_CHANGE event renamed to wxEVT_GRID_CELL_CHANGED and shouldn't - wxEVT_GRID_CELL_CHANGE event renamed to wxEVT_GRID_CELL_CHANGED and shouldn't
be vetoed any more, use the new wxEVT_GRID_CELL_CHANGING event to do it. be vetoed any more, use the new wxEVT_GRID_CELL_CHANGING event to do it.
- Now wxWidgets at startup in debug builds checks if all wxEvent-derived classes
correctly implement the Clone() function, logging a warning if they don't.
A correct implementation for MyCustomEventClass::Clone() is simply:
virtual wxEvent *Clone() const { return new MyCustomEventClass(*this); }
- Global wxPendingEvents and wxPendingEventsLocker objects were removed. - Global wxPendingEvents and wxPendingEventsLocker objects were removed.
You may use wxEventLoopBase::SuspendProcessingOfPendingEvents instead of You may use wxEventLoopBase::SuspendProcessingOfPendingEvents instead of
locking wxPendingEventsLocker now. locking wxPendingEventsLocker now.