Class: Wx::EventCategory
Overview
The different categories for a Event; see Wx::Event#get_event_category.
They are used as OR-combinable flags by Wx::EventLoopBase::YieldFor.
Constant Summary collapse
- EVT_CATEGORY_UI =
This is the category for those events which are generated to update the appearance of the GUI but which (usually) do not comport data processing, i.e.
Wx::EventCategory.new(1)
- EVT_CATEGORY_USER_INPUT =
This category groups those events which are generated directly from the user through input devices like mouse and keyboard and usually result in data to be processed from the application (e.g.
Wx::EventCategory.new(2)
- EVT_CATEGORY_SOCKET =
This category is for SocketEvent.
Wx::EventCategory.new(4)
- EVT_CATEGORY_TIMER =
This category is for TimerEvent.
Wx::EventCategory.new(8)
- EVT_CATEGORY_THREAD =
This category is for any event used to send notifications from the secondary threads to the main one or in general for notifications among different threads (which may or may not be user-generated).
Wx::EventCategory.new(16)
- EVT_CATEGORY_ALL =
This mask is used in Wx::EventLoopBase::YieldFor to specify that all event categories should be processed.
Wx::EventCategory.new(127)
Method Summary
Methods inherited from Enum
#!, #&, #<=>, #allbits?, #anybits?, #coerce, #eql?, #initialize, #inspect, #integer?, #method_missing, #nobits?, #real?, #succ, #to_int, #to_s, #|, #~
Constructor Details
This class inherits a constructor from Wx::Enum
Dynamic Method Handling
This class handles dynamic methods through the method_missing method in the class Wx::Enum