+- Default location of wxFileConfig files has changed under Windows, you will
+ need to update your code if you access these files directly.
+
+- wxWindow::IsEnabled() now returns false if a window parent (and not
+ necessarily the window itself) is disabled, new function IsThisEnabled()
+ with the same behaviour as old IsEnabled() was added.
+
+- Generating wxNavigationKeyEvent events doesn't work any more under wxGTK (and
+ other platforms in the future), use wxWindow::Navigate() or NavigateIn()
+ instead.
+
+- Sizers distribute only the extra space between the stretchable items
+ according to their proportions and not all available space. We believe the
+ new behaviour corresponds better to user expectations but if you did rely
+ on the old behaviour you will have to update your code to set the minimal
+ sizes of the sizer items to be in the same proportion as the items
+ proportions to return to the old behaviour.
+
+- wxWindow::Freeze/Thaw() are not virtual any more, if you overrode them in
+ your code you need to override DoFreeze/Thaw() instead now.
+
+- wxCalendarCtrl has native implementation in wxGTK, but it has less features
+ than the generic one. The native implementation is used by default, but you
+ can still use wxGenericCalendarCtrl instead of wxCalendarCtrl in your code if
+ you need the extra features.
+
+- wxDocument::FileHistoryLoad() and wxFileHistory::Load() now take const
+ reference to wxConfigBase argument and not just a reference, please update
+ your code if you overrode these functions and change the functions in the
+ derived classes to use const reference as well.
+
+- Calling wxConfig::Write() with an enum value will fail to compile because
+ wxConfig now tries to convert all unknown types to wxString automatically
+ using wxToString() function.
+
+ The simplest solution is to cast the enum value to int, e.g.
+ @code
+ enum Colour { Red, Green, Blue };
+
+ wxConfig conf;
+ conf.Write("MyFavouriteColour", Red); // ERROR: no match
+ conf.Write("MyFavouriteColour", int(Red)); // OK
+ @endcode
+
+ Another possibility which exists now is to provide an overload of
+ wxToString() (and wxFromString()) for your own type, e.g.
+
+ @code
+ wxString wxToString(Colour col)
+ {
+ return col == Red ? "R" : col == Green ? "G" : "B";
+ }
+
+ bool wxFromString(const wxString& s, Colour* col)
+ {
+ if ( s.length() != 1 )
+ return false;
+
+ switch ( s[0].GetValue() )
+ {
+ case 'R': *col = Red; return true;
+ case 'G': *col = Green; return true;
+ case 'B': *col = Blue; return true;
+ }
+
+ return false;
+ }
+ @endcode
+
+ Of course, this will change the format of the wxConfig output which may be
+ undesirable.
+
+- wxTE_AUTO_SCROLL style is deprecated as it's always on by default anyhow in
+ the ports which support it so you should simply remove any mentions of it
+ from your code.
+
+- If you use wxScrolled<T>::SetTargetWindow() you must override
+ wxScrolled<T>::GetSizeAvailableForScrollTarget() method to compute the size
+ available for the scroll target as function of the main window size, please
+ see the documentation of this method for more details.
+
+- Signatures of wxDataViewCustomRenderer::Activate(),
+ wxDataViewCustomRenderer::LeftClick() and
+ wxDataViewCustomRenderer::StartDrag() virtual methods changed. You will need
+ to change them in your derived renderer class too if you override them.
projects / wxWidgets.git / blobdiff