Lines Matching refs:can
8 how you can modify your application to be 2.0-compliant.
21 of 2.0 will ensure that wxWidgets can continue to evolve for the foreseeable
28 Even before compiling with version 2.0, there's also a lot you can do right now to make porting
42 because in 2.0, you can't use GetDC() and wxDCs are not persistent.
84 wxPropertyFormView can be used in a wxForm-like way, except that you specify a pre-constructed panel
85 or dialog; or you can use a wxPropertyListView to show attributes in a scrolling list - you don't even need
121 Control commands, such as button commands, can be routed to a derived button class,
127 To intercept other events, you used to override virtual functions, such as OnSize. Now, while you can use
130 including OnClose (although in fact you can still use the old, virtual form of OnClose for the time being).
138 which can be drawn into). The status bar has become a class in its own right, wxStatusBar.
155 who the object belongs to: it can pass the reference, then destroy the object without
158 For the purposes of code migration, you can use the old style of object management - maintaining
175 which can do away with dialog layout issues altogether by presenting a list of editable
232 Instead, you create a temporary device context, which means that any window or control can be drawn
235 you use a wxClientDC or wxWindowDC. You can still parameterise your drawing code so that it
258 returned in wxWidgets 1.xx, your application will need to be changed. Usually you can
281 empty string (``") or a null string. You can check for a null string with wxString::IsNull().
346 MDI is now implemented as a family of separate classes, so you can't switch to MDI just by
375 However, if you wish to intercept different events using different functions, you can