Lines Matching defs:wxWidgets
1 \chapter{Porting from wxWidgets 1.xx}\label{porting}
4 version 1.xx of wxWidgets to version 2.0.
12 the wxWidgets 2.0 API has far more in common with 1.xx than it has differences.
21 of 2.0 will ensure that wxWidgets can continue to evolve for the foreseeable
56 for some notes on using member functions for callbacks. wxWidgets 2.0 will banish global
73 wxWidgets functions (except when you need to save the pointer if deallocation is required), there should
79 Windows and X under wxWidgets 1.66. Yes, this is not easy... but I think it is better to conform to the
88 Because wxForm uses a number of features to be dropped in wxWidgets 2.0, it cannot be
93 MDI sample is. In wxWidgets 2.0, MDI functionality is separated into distinct classes.
98 The way that events are handled has been radically changed in wxWidgets 2.0. Please
99 read the topic `Event handling overview' in the wxWidgets 2.0 manual for background
221 Note that wxForm is no longer supported in wxWidgets 2.0. Consider using the wxPropertyFormView class
228 In wxWidgets 2.0, device contexts are used for drawing into, as per 1.xx, but the way
257 However, when a wxString is returned from a function in wxWidgets 2.0 where a char* was
258 returned in wxWidgets 1.xx, your application will need to be changed. Usually you can
296 Some wxWidgets 1.xx functionality has been left to ease the transition to 2.0. This functionality