]>
Commit | Line | Data |
---|---|---|
1 | ------------------------ | |
2 | wxWidgets 2.5 Change Log | |
3 | ------------------------ | |
4 | ||
5 | INCOMPATIBLE CHANGES SINCE 2.4.x | |
6 | ================================ | |
7 | ||
8 | Please take a few minutes to read the following list, especially | |
9 | paying attention to the most important changes which are marked | |
10 | with '!' in the first column. | |
11 | ||
12 | Also please note that you should ensure that WXWIN_COMPATIBILITY_2_4 | |
13 | is defined to 1 if you wish to retain maximal compatibility with 2.4 | |
14 | series. | |
15 | ||
16 | ! windows are no longer fully repainted when resized, use new style | |
17 | wxFULL_REPAINT_ON_RESIZE to force this (wxNO_FULL_REPAINT_ON_RESIZE still | |
18 | exists but doesn't do anything any more, this behaviour is default now) | |
19 | ||
20 | ! wxWindow::m_font and m_backgroundColour/m_foregroundColour are no longer | |
21 | always set, use GetFont(), GetBack/ForegroundColour() to access | |
22 | them, and they will be dynamically determined if necessary. | |
23 | ||
24 | ||
25 | ! The Sizers have had some fundamental internal changes in the 2.5.2 | |
26 | and 2.5.3 releases intended to make them do more of the "Right | |
27 | Thing" but also be as backwards compatible as possible. First a bit | |
28 | about how things used to work: | |
29 | ||
30 | * The size that a window had when Add()ed to the sizer was assumed | |
31 | to be its minimal size, and that size would always be used by | |
32 | default when calculating layout size and positions, and the | |
33 | sizer itself would keep track of that minimal size. | |
34 | ||
35 | * If the window item was Add()ed with the wxADJUST_MINSIZE flag | |
36 | then when layout was calculated the item's GetBestSize would be | |
37 | used to reset the minimal size that the sizer used. | |
38 | ||
39 | The main thrust of the new Sizer changes was to make behaviour like | |
40 | wxADJUST_MINSIZE be the default, and also to push the tracking of | |
41 | the minimal size to the window itself (since it knows its own needs) | |
42 | instead of having the sizer take care of it. Consequently these | |
43 | changes were made: | |
44 | ||
45 | * The wxFIXED_MINSIZE flag was added to allow for the old | |
46 | behaviour. When this flag is used the size a window has when | |
47 | Add()ed to the sizer will be treated as its minimal size and it | |
48 | will not be readjusted on each layout. | |
49 | ||
50 | * The min size stored in wxWindow and settable with SetSizeHints or | |
51 | SetMinSize will by default be used by the sizer (if it was set) | |
52 | as the minimal size of the sizer item. If the minsize was not | |
53 | set (or was only partially set) then the window's best size is | |
54 | fetched and it is used instead of (or blended with) the minsize. | |
55 | wxWindow:GetBestFittingSize was added to facilitate getting the | |
56 | size to be used by the sizers. | |
57 | ||
58 | * The best size of a window is cached so it doesn't need to | |
59 | recalculated on every layout. wxWindow::InvalidateBestSize was | |
60 | added and should be called (usually just internally in control | |
61 | methods) whenever something is done that would make the best | |
62 | size change. | |
63 | ||
64 | * All wxControls were changed to set the minsize to what is passed | |
65 | to the constructor or Create method, and also to set the real | |
66 | size of the control to the blending of the minsize and bestsize. | |
67 | wxWindow::SetBestFittingSize was added to help with this, | |
68 | although most controls don't need to call it directly because it | |
69 | is called indirectly via the SetInitialSize called in the base | |
70 | classes. | |
71 | ||
72 | At this time, the only situation known not to work the same as | |
73 | before is the following: | |
74 | ||
75 | win = new SomeWidget(parent); | |
76 | win->SetSize(SomeNonDefaultSize); | |
77 | sizer->Add(win); | |
78 | ||
79 | In this case the old code would have used the new size as the | |
80 | minimum, but now the sizer will use the default size as the minimum | |
81 | rather than the size set later. It is an easy fix though, just move | |
82 | the specification of the size to the constructor (assuming that | |
83 | SomeWidget will set its minsize there like the rest of the controls | |
84 | do) or call SetMinSize instead of SetSize. | |
85 | ||
86 | In order to fit well with this new scheme of things, all wxControls | |
87 | or custom controls should do the following things. (Depending on | |
88 | how they are used you may also want to do the same thing for | |
89 | non-control custom windows.) | |
90 | ||
91 | * Either override or inherit a meaningful DoGetBestSize method | |
92 | that calculates whatever size is "best" for the control. Once | |
93 | that size is calculated then there should normally be a call to | |
94 | CacheBestSize to save it for later use, unless for some reason | |
95 | you want the best size to be recalculated on every layout. | |
96 | ||
97 | * Any method that changes the attributes of the control such that | |
98 | the best size will change should call InvalidateBestSize so it | |
99 | will be recalculated the next time it is needed. | |
100 | ||
101 | * The control's constructor and/or Create method should ensure | |
102 | that the minsize is set to the size passed in, and that the | |
103 | control is sized to a blending of the min size and best size. | |
104 | This can be done by calling SetBestFittingSize. | |
105 | ||
106 | ||
107 | ||
108 | - no initialization/cleanup can be done in wxApp/~wxApp because they are | |
109 | now called much earlier/later than before; please move any exiting code | |
110 | from there to wxApp::OnInit()/OnExit() | |
111 | - also, OnExit() is not called if OnInit() fails | |
112 | - finally the program exit code is OnRun() return value, not OnExit() one | |
113 | - wxTheApp can't be assigned to any longer, use wxApp::SetInstance() instead | |
114 | - wxFileType::GetIcon() returns wxIconLocation, not wxIcon | |
115 | - wxColourDatabase is not a wxList any more, use AddColour to add new colours | |
116 | - wxWindow::Clear() is now called ClearBackground() | |
117 | - pointer returned by wxFont::GetNativeFontInfo() must not be deleted now | |
118 | - wxMouseEvent::Moving() doesn't return true if mouse is being dragged any more | |
119 | - (most) controls now inherit parents colours by default, override | |
120 | ShouldInheritColours() to return false if you don't want this to happen | |
121 | - wxApp::SendIdleEvent() now takes 2 arguments | |
122 | - wxTabView::GetLayers() changed return type from wxList& to wxTabLayerList& | |
123 | (when WXWIN_COMPATIBILITY_2_4 == 0) | |
124 | - wxID_SEPARATOR (id used for the menu separators) value changed from -1 to -2 | |
125 | - wxGetNumberFromUser() is now in separate wx/numdlg.h, not wx/textdlg.h | |
126 | - wxChoice and wxCombobox now handle their size in the same way as in all the | |
127 | other ports under MSW, new code is actually correct but different from weird | |
128 | stuff they were doing before so the behaviour of your programs might change | |
129 | - wxTaskBarIcon objects must now be destroyed before the application can exit. | |
130 | Previously, the application terminated if there were no top level windows; | |
131 | now it terminates if there are no top level windows or taskbar icons left. | |
132 | - wxZlibInputStream is not by default compatible with the output of the | |
133 | 2.4.x version of wxZlibOutputStream. However, there is a compatibility mode, | |
134 | switched on by passing wxZLIB_24COMPATIBLE to the constructor. | |
135 | - when WXWIN_COMPATIBILITY_2_4 == 0 wxHashTable uses a new implementation | |
136 | not using wxList keyed interface (the same used when wxUSE_STL == 1), | |
137 | the only incompatibility being that Next() returns a wxHashTable::Node* | |
138 | instead of a wxNode*. | |
139 | - non-const wxDC methods GetBackground(), GetBrush(), GetFont() and GetPen() | |
140 | as well as wxWindow methods GetFont() and GetCursor() don't exist any more, | |
141 | please fix your code -- it never worked correctly anyhow if you modified the | |
142 | objects returned by these methods so you should simply switch to using const | |
143 | methods. | |
144 | - wxWindow::GetFont() now returns wxFont object instead of reference | |
145 | - EVT_XXX macros are now type-safe; code that uses wrong type for event | |
146 | handler's argument will no longer compile. | |
147 | - Identical functionality of wxFileDialog::ParseWildcard, | |
148 | wxGenericDirCtrl::ParseFilter, Motif and MSW parsing native dialogs | |
149 | is now accessible in ::wxParseCommonDialogsFilter | |
150 | - wxNotebookSizer and wxBookCtrlSizer are now deprecated -- they are no longer | |
151 | needed, you can treat wxNotebook as any other control and put it directly | |
152 | into the sizer that was wxNotebookSizer's parent sizer in old code. | |
153 | - wxFile methods now return either wxFileOffset or wxFileSize_t which may be a | |
154 | 64 bit integer type, even on 32 bit platforms, instead of off_t and so the | |
155 | return value of wxFile::Length(), for example, shouldn't be assigned to off_t | |
156 | variable any more (the compiler might warn you about this) | |
157 | - wxListItem::m_data is now of type wxUIntPtr, not long, for compatibility | |
158 | with 64 bit systems | |
159 | ||
160 | ||
161 | DEPRECATED METHODS SINCE 2.4.x | |
162 | ============================== | |
163 | ||
164 | Deprecated methods may still be used but will disappear in future wxWidgets | |
165 | versions, please update your code to not use them. | |
166 | ||
167 | - wxDocManager::GetNoHistoryFiles() renamed to GetHistoryFilesCount() | |
168 | - wxSizer::Remove(wxWindow *), use Detach() instead [it is more clear] | |
169 | - wxSizer::Set/GetOption(): use Set/GetProportion() instead | |
170 | - wxKeyEvent::KeyCode(): use GetKeyCode instead | |
171 | - wxList::Number, First, Last, Nth: use GetCount, GetFirst/Last, Item instead | |
172 | - wxNode::Next, Previous, Data: use GetNext, GetPrevious, GetData instead | |
173 | - wxListBase::operator wxList&(): use typesafe lists instead | |
174 | - wxTheFontMapper: use wxFontMapper::Get() instead | |
175 | - wxStringHashTable: use wxHashMap instead | |
176 | - wxHashTableLong: use wxHashMap instead | |
177 | - wxArrayString::GetStringArray: use wxCArrayString or alternative wxWidgets | |
178 | methods taking wxArrayString | |
179 | - wxArrayString::Remove(index, count): use RemoveAt instead | |
180 | - wxTreeItemId conversion to long is deprecated and shouldn't be used | |
181 | - wxTreeCtrl::GetFirst/NextChild() 2nd argument now has type wxTreeItemIdValue | |
182 | and not long, please change declarations of "cookie"s in your code | |
183 | accordingly -- otherwise your code won't work on 64 bit platforms | |
184 | - [MSW only] wxWindow::GetUseCtl3D(), GetTransparentBackground() and | |
185 | SetTransparent() as well as wxNO_3D and wxUSER_COLOURS styles | |
186 | - wxList keyed interface: use wxHashMap instead | |
187 | - wxColourDatabase::FindColour(): use Find() instead (NB: different ret type) | |
188 | - wxHashTable::Next: use wxHashTable::Node* or | |
189 | wxHashTable::compatibility_iterator to store the return | |
190 | value | |
191 | - wxWave class; use wxSound instead | |
192 | - The wxHIDE_READONLY flag for wxFileDialog was not implemented | |
193 | and has now been removed | |
194 | - wxTaskBarIcon::OnXXX() virtual methods: use events instead | |
195 | - obsolete and not used wxUSE_GENERIC_DIALOGS_IN_MSW has been removed | |
196 | - wxDbTable::wxDbTable with wxChar* deprecated, same with wxString& instead | |
197 | ||
198 | ||
199 | OTHER CHANGES | |
200 | ============= | |
201 | ||
202 | 2.5.4 | |
203 | ----- | |
204 | ||
205 | All: | |
206 | ||
207 |