Lines Matching refs:can
116 // event can be processed either in the base wxWidgets class
172 some reason, you can use
225 While generically \helpref{wxEvents}{wxevent} can be generated both by user
239 \twocolitem{All \helpref{wxTextCtrl}{wxtextctrl} methods}{\helpref{wxTextCtrl::ChangeValue}{wxtextctrlchangevalue} can be used instead
258 % each window can handle its own commands and UI updates independently. In
259 % fact wxTextCtrl can handle Cut, Copy, Paste, Undo and Redo commands and UI update
266 if you don't want to. You can derive a new class from wxEvtHandler instead,
270 event handler the object that responds to events. This way, you can avoid
280 in your application that changes aspects of dialog boxes. You can
283 has derived new classes to customize behaviour, your utility can indulge
286 don't want them to diverge from the lesson. Here, you can examine the events
295 uniquely determine window identity in the event system (though you can use it
312 The following standard identifiers are supplied. You can use wxID\_HIGHEST to
314 you can use identifiers below wxID\_LOWEST.
407 \twocolitem{\helpref{wxMouseEvent}{wxmouseevent}}{Mouse event macros can handle either individual
452 You can ignore the {\it value} parameter of the DECLARE\_EVENT\_TYPE macro
462 a new event type, you can then use one of the generic event table macros