wxruby3 0.9.3-x64-mingw-ucrt → 0.9.5-x64-mingw-ucrt

data/lib/wx/doc/gen/pg/pg_property.rb

@@ -321,7 +321,6 @@ module Wx::PG
   # - Creating Custom Properties
   # 
   # ## Supplied Ready-to-use Property Classes
-  # 
   # Here is a list and short description of supplied fully-functional property classes. They are located in either {Wx::props.h} or {Wx::advprops.h}.
   # 
   # - {Wx::PG::ArrayStringProperty} 
@@ -365,11 +364,9 @@ module Wx::PG
   # - {Wx::PG::UIntProperty}
   # 
   # ## wxPropertyCategory
-  # 
   # Not an actual property per se, but a header for a group of properties. Regardless inherits from {Wx::PG::PGProperty}, and supports displaying 'labels' for columns other than the first one. Easiest way to set category's label for second column is to call {Wx::PG::PGProperty#set_value} with string argument.
   # 
   # ## wxStringProperty
-  # 
   # Simple string property.
   # Supported special attributes:
   # 
@@ -383,7 +380,6 @@ module Wx::PG
   # </div>
   # 
   # ## wxIntProperty
-  # 
   # It derives from {Wx::PG::NumericProperty} and displays value as a signed long integer. {Wx::PG::IntProperty} seamlessly supports 64-bit integers (i.e. {Wx::LongLong}) on overflow. To safely convert variant to integer, use code like this:
   # 
   # ```
@@ -423,7 +419,6 @@ module Wx::PG
   # - {Wx::PG::PG_ATTR_SPINCTRL_STEP}, {Wx::PG::PG_ATTR_SPINCTRL_WRAP}, {Wx::PG::PG_ATTR_SPINCTRL_MOTION}: Sets SpinCtrl editor parameters. 
   # 
   # ## wxUIntProperty
-  # 
   # Like {Wx::PG::IntProperty}, but displays value as unsigned int. To set the prefix used globally, manipulate {Wx::PG::PG_UINT_PREFIX} string attribute. To set the globally used base, manipulate {Wx::PG::PG_UINT_BASE} int attribute. Regardless of current prefix, understands (hex) values starting with both "0x" and "$" (apart from edit mode). Like {Wx::PG::IntProperty}, {Wx::PG::UIntProperty} seamlessly supports 64-bit unsigned integers (i.e. {Wx::ULongLong}). Same {Wx::Variant} safety rules apply.
   # Supported special attributes:
   # 
@@ -439,7 +434,6 @@ module Wx::PG
   # </div>
   # 
   # ## wxFloatProperty
-  # 
   # Like {Wx::PG::StringProperty}, but converts text to a double-precision floating point. Default float-to-text precision is 6 decimals, but this can be changed by modifying {Wx::PG::PG_FLOAT_PRECISION} attribute.
   # Note that when displaying the value, sign is omitted if the resulting textual representation is effectively zero (for example, -0.0001 with precision of 3 will become 0.0 instead of -0.0). This behaviour is unlike what C standard library does, but should result in better end-user experience in almost all cases.
   # Supported special attributes:
@@ -449,7 +443,6 @@ module Wx::PG
   # - {Wx::PG::PG_ATTR_SPINCTRL_STEP}, {Wx::PG::PG_ATTR_SPINCTRL_WRAP}, {Wx::PG::PG_ATTR_SPINCTRL_MOTION}: Sets SpinCtrl editor parameters. 
   # 
   # ## wxBoolProperty
-  # 
   # Represents a boolean value. {Wx::Choice} is used as editor control, by the default. {Wx::PG::PG_BOOL_USE_CHECKBOX} attribute can be set to true in order to use check box instead.
   # Supported special attributes:
   # 
@@ -457,7 +450,6 @@ module Wx::PG
   # - {Wx::PG::PG_BOOL_USE_DOUBLE_CLICK_CYCLING}: If set to true cycles combo box instead showing the list. 
   # 
   # ## wxLongStringProperty
-  # 
   # Like {Wx::PG::StringProperty}, but has a button that triggers a small text editor dialog. Note that in long string values, some control characters are escaped: tab is represented by "\t", line break by "\n", carriage return by "\r" and backslash character by "\\". If another character is preceded
   # by backslash, the backslash is skipped.
   # Note also that depending on the system (port), some sequences of special
@@ -597,7 +589,6 @@ module Wx::PG
   # - {Wx::PG::PG_FILE_INITIAL_PATH}: Sets the initial path of where to look for files. 
   # 
   # ## wxColourProperty
-  # 
   # <b>Useful alternate editor:</b> Choice.
   # Represents {Wx::Colour}. {Wx::Button} is used to trigger a colour picker dialog. There are various sub-classing opportunities with this class. See below in {Wx::PG::SystemColourProperty} section for details.
   # Supported special attributes:
@@ -605,14 +596,12 @@ module Wx::PG
   # - {Wx::PG::PG_COLOUR_HAS_ALPHA}: If set to true allows user to edit the alpha colour component. 
   # 
   # ## wxFontProperty
-  # 
   # Represents {Wx::Font}. Various sub-properties are used to edit individual subvalues.
   # Supported special attributes:
   # 
   # - {Wx::PG::PG_DIALOG_TITLE}: Sets a specific title for the font dialog.
   # 
   # ## wxSystemColourProperty
-  # 
   # Represents {Wx::Colour} and a system colour index. {Wx::Choice} is used to edit the value. Drop-down list has color images. Note that value type is {Wx::PG::ColourPropertyValue} instead of {Wx::Colour} (which {Wx::PG::ColourProperty} uses).
   # 
   # In {Wx::PG::SystemColourProperty}, and its derived class {Wx::PG::ColourProperty}, there are various sub-classing features. To set a basic list of colour names, call {Wx::PG::PGProperty#set_choices}.
@@ -635,11 +624,9 @@ module Wx::PG
   # ```
   # 
   # ## wxCursorProperty
-  # 
   # Represents a {Wx::Cursor}. {Wx::Choice} is used to edit the value. Drop-down list has cursor images under some (WXMSW) platforms.
   # 
   # ## Creating Custom Properties
-  # 
   # New properties can be created by subclassing {Wx::PG::PGProperty} or one of the provided property classes, and (re)implementing necessary member functions. Below, each virtual member function has ample documentation about its purpose and any odd details which to keep in mind.
   # Here is a very simple 'template' code:
   # 

data/lib/wx/doc/gen/pg/pg_validation_info.rb

@@ -15,7 +15,6 @@ module Wx::PG
   # 
   # 
   # ## wxPropertyGrid Window Styles
-  # 
   # SetWindowStyleFlag method can be used to modify some of these at run-time.
   # 
   # @wxrb_require USE_PROPGRID
@@ -192,7 +191,6 @@ module Wx::PG
   # 
   # 
   # ## wxPropertyGrid Action Identifiers
-  # 
   # These are used with {Wx::PG::PropertyGrid#add_action_trigger} and {Wx::PG::PropertyGrid#clear_action_triggers}.
   # 
   # @wxrb_require USE_PROPGRID

data/lib/wx/doc/gen/pg/property_grid.rb

@@ -13,11 +13,9 @@ module Wx::PG
   # See also wxPropertyGrid Overview.
   # 
   # ## Window Styles
-  # 
   # See wxPropertyGrid Window Styles.
   # 
   # ## Event Handling
-  # 
   # Please see {Wx::PG::PropertyGridEvent} for the documentation of all event types you can use with {Wx::PG::PropertyGrid}.
   # 
   # <div class="wxrb-remark">

data/lib/wx/doc/gen/pg/property_grid_event.rb

@@ -47,7 +47,7 @@ module Wx::PG
   
     # @overload initialize(commandType=0, id=0)
     #   Constructor.
-    #   @param commandType [Wx::StaticLine::EventType] 
+    #   @param commandType [Wx::Notebook::EventType] 
     #   @param id [Integer] 
     #   @return [Wx::PG::PropertyGridEvent]
     # @overload initialize(event)

data/lib/wx/doc/gen/pg/property_grid_interface.rb

@@ -655,12 +655,12 @@ module Wx::PG
     # @param src [String]  String generated by SaveEditableState.
     # @param restoreStates [Integer]  Which parts to restore from source string. See list of editable state flags.
     # @return [Boolean]
-    def restore_editable_state(src, restoreStates=Wx::PG::PropertyGridManager::EditableStateFlags::AllStates) end
+    def restore_editable_state(src, restoreStates=Wx::PG::PropertyGridPage::EditableStateFlags::AllStates) end
     
     # Used to acquire user-editable state (selected property, expanded properties, scrolled position, splitter positions).
     # @param includedStates [Integer]  Which parts of state to include. See list of editable state flags.
     # @return [String]
-    def save_editable_state(includedStates=Wx::PG::PropertyGridManager::EditableStateFlags::AllStates) end
+    def save_editable_state(includedStates=Wx::PG::PropertyGridPage::EditableStateFlags::AllStates) end
     
     # Set proportion of an auto-stretchable column.
     # 

data/lib/wx/doc/gen/pg/property_grid_manager.rb

@@ -49,11 +49,9 @@ module Wx::PG
   # ```
   # 
   # ## Window Styles
-  # 
   # See wxPropertyGrid Window Styles.
   # 
   # ## Event Handling
-  # 
   # See wxPropertyGrid Event Handling for more information.
   # 
   # Category:  {Wx::PG::PropertyGrid}

data/lib/wx/doc/gen/pg/property_grid_page.rb

@@ -9,7 +9,6 @@ module Wx::PG
   # 
   # 
   # ## wxPropertyGridIterator Flags
-  # 
   # NOTES: At lower 16-bits, there are flags to check if item will be included. At higher 16-bits, there are same flags, but to instead check if children will be included.
   # 
   # @wxrb_require USE_PROPGRID
@@ -76,7 +75,6 @@ module Wx::PG
   # Please note that most member functions are inherited and as such not documented on this page. This means you will probably also want to read {Wx::PG::PropertyGridInterface} class reference.
   # 
   # ## Event Handling
-  # 
   # {Wx::PG::PropertyGridPage} receives events emitted by its {Wx::PG::PropertyGridManager}, but only those events that are specific to that page. If {Wx::PG::PropertyGridPage}:: IsHandlingAllEvents returns false, then unhandled events are sent to the manager's parent, as usual.
   # See wxPropertyGrid Event Handling for more information.
   # 

data/lib/wx/doc/gen/pg/property_grid_page_state.rb

@@ -121,7 +121,6 @@ module Wx::PG
   # 
   # 
   # ## wxPropertyGridHitTestResult
-  # 
   # A return value from {Wx::PG::PropertyGrid#hit_test}, contains all you need to know about an arbitrary location on the grid.
   # 
   # 

data/lib/wx/doc/gen/prt/post_script_dc.rb

@@ -11,7 +11,6 @@ module Wx::PRT
   # See {Wx::DC} for descriptions of the member functions.
   # 
   # ## Starting a document
-  # 
   # Document should be started with call to {Wx::PRT::PostScriptDC#start_doc} prior to calling any function to execute a drawing operation. However, some functions, like {Wx::PRT::PostScriptDC#set_font}, may be legitimately called even before {Wx::PRT::PostScriptDC#start_doc}.
   # 
   # Category:  Device Contexts

data/lib/wx/doc/gen/rbn/ribbon_bar_event.rb

@@ -18,7 +18,7 @@ module Wx::RBN
   class RibbonBarEvent < NotifyEvent
   
     # Constructor.
-    # @param command_type [Wx::StaticLine::EventType] 
+    # @param command_type [Wx::Notebook::EventType] 
     # @param win_id [Integer] 
     # @param page [Wx::RBN::RibbonPage] 
     # @return [Wx::RBN::RibbonBarEvent]

data/lib/wx/doc/gen/rbn/ribbon_button_bar_event.rb

@@ -19,7 +19,7 @@ module Wx::RBN
   class RibbonButtonBarEvent < CommandEvent
   
     # Constructor.
-    # @param command_type [Wx::StaticLine::EventType] 
+    # @param command_type [Wx::Notebook::EventType] 
     # @param win_id [Integer] 
     # @param bar [Wx::RBN::RibbonButtonBar] 
     # @param button [Integer] 

data/lib/wx/doc/gen/rbn/ribbon_gallery_event.rb

@@ -16,7 +16,7 @@ module Wx::RBN
   class RibbonGalleryEvent < CommandEvent
   
     # Constructor.
-    # @param command_type [Wx::StaticLine::EventType] 
+    # @param command_type [Wx::Notebook::EventType] 
     # @param win_id [Integer] 
     # @param gallery [Wx::RBN::RibbonGallery] 
     # @param item [Integer] 

data/lib/wx/doc/gen/rbn/ribbon_panel_event.rb

@@ -18,7 +18,7 @@ module Wx::RBN
   class RibbonPanelEvent < CommandEvent
   
     # Constructor.
-    # @param command_type [Wx::StaticLine::EventType] 
+    # @param command_type [Wx::Notebook::EventType] 
     # @param win_id [Integer] 
     # @param panel [Wx::RBN::RibbonPanel] 
     # @return [Wx::RBN::RibbonPanelEvent]

data/lib/wx/doc/gen/rbn/ribbon_tool_bar_event.rb

@@ -13,7 +13,7 @@ module Wx::RBN
   # @wxrb_require USE_RIBBON
   class RibbonToolBarEvent < CommandEvent
   
-    # @param command_type [Wx::StaticLine::EventType] 
+    # @param command_type [Wx::Notebook::EventType] 
     # @param win_id [Integer] 
     # @param bar [Wx::RBN::RibbonToolBar] 
     # @return [Wx::RBN::RibbonToolBarEvent]

data/lib/wx/doc/gen/rtc/rich_text_event.rb

@@ -58,7 +58,7 @@ module Wx::RTC
   
     # @overload initialize(commandType=Wx::EVT_NULL, winid=0)
     #   Constructor.
-    #   @param commandType [Wx::StaticLine::EventType]  The type of the event.
+    #   @param commandType [Wx::Notebook::EventType]  The type of the event.
     #   @param winid [Integer]  Window identifier. The value {Wx::StandardID::ID_ANY} indicates a default value.
     #   @return [Wx::RTC::RichTextEvent]
     # @overload initialize(event)

data/lib/wx/doc/gen/rtc/rich_text_html_handler.rb

@@ -15,7 +15,6 @@ module Wx::RTC
   # You can call {Wx::RTC::RichTextHTMLHandler#get_temporary_image_locations} to get the array of temporary image names.
   # 
   # ## Handler flags
-  # 
   # The following flags can be used with this handler, via the handler's {Wx::RTC::RichTextHTMLHandler#set_flags} function or the buffer or control's SetHandlerFlags() function:
   # 
   # - {Wx::RTC::RICHTEXT_HANDLER_SAVE_IMAGES_TO_MEMORY} Images are saved to the memory filesystem: suitable for showing {Wx::HTML} windows.

data/lib/wx/doc/gen/rtc/rich_text_style_list_box.rb

@@ -304,6 +304,9 @@ module Wx::RTC
     # @return [void]
     def update_styles; end
     
+    
+    protected
+    
   end # RichTextStyleComboCtrl
   
 

data/lib/wx/doc/gen/rtc/rich_text_xml_handler.rb

@@ -11,7 +11,6 @@ module Wx::RTC
   # You can either add the handler to the buffer and load and save through the buffer or control API, or you can create an instance of the handler on the stack and call its functions directly.
   # 
   # ## Handler flags
-  # 
   # The following flags can be used with this handler, via the handler's {Wx::RTC::RichTextXMLHandler#set_flags} function or the buffer or control's SetHandlerFlags() function:
   # 
   # - {Wx::RTC::RICHTEXT_HANDLER_INCLUDE_STYLESHEET} Include the style sheet in loading and saving operations.

data/lib/wx/doc/gen/scroll_bar.rb

@@ -70,7 +70,6 @@ module Wx
   # - {Wx::EvtHandler#evt_command_scroll_changed}(meth = nil, &block): Process {Wx::EVT_SCROLL_CHANGED} end of scrolling events (MSW only). 
   # 
   # ## The difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED
-  # 
   # The EVT_SCROLL_THUMBRELEASE event is only emitted when actually dragging the thumb using the mouse and releasing it (This EVT_SCROLL_THUMBRELEASE event is also followed by an EVT_SCROLL_CHANGED event).
   # The EVT_SCROLL_CHANGED event also occurs when using the keyboard to change the thumb position, and when clicking next to the thumb (In all these cases the EVT_SCROLL_THUMBRELEASE event does not happen).
   # In short, the EVT_SCROLL_CHANGED event is triggered when scrolling/moving has finished independently of the way it had started. Please see the Widgets Sample ("Slider" page) to see the difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED in action.

data/lib/wx/doc/gen/sizer.rb

@@ -36,7 +36,6 @@ module Wx
   # Please notice that sizers, like child windows, are owned by the library and will be deleted by it which implies that they must be allocated on the heap. However if you create a sizer and do not add it to another sizer or window, the library wouldn't be able to delete such an orphan sizer and in this, and only this, case it should be deleted explicitly.
   # 
   # ## wxSizer flags
-  # 
   # The "flag" argument accepted by {Wx::SizerItem} constructors and other functions, e.g. {Wx::Sizer#add}, is an OR-combination of the following flags. Two main behaviours are defined using these flags. One is the border around a window: the border parameter determines the border width whereas the flags given here determine which side(s) of the item that the border will be added. The other flags determine how the sizer item behaves when the space allotted to the sizer changes, and is somewhat dependent on the specific kind of sizer used.
   # 
   # {Wx::Direction::TOP}

data/lib/wx/doc/gen/slider.rb

@@ -132,7 +132,6 @@ module Wx
   # - {Wx::EvtHandler#evt_slider}(id, meth = nil, &block): Process {Wx::EVT_SLIDER} which is generated after any change of {Wx::Slider} position in addition to one of the events above. Notice that the handler of this event receives a {Wx::CommandEvent} as argument and not {Wx::ScrollEvent}, as all the other handlers. 
   # 
   # ## The difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED
-  # 
   # The EVT_SCROLL_THUMBRELEASE event is only emitted when actually dragging the thumb using the mouse and releasing it (This EVT_SCROLL_THUMBRELEASE event is also followed by an EVT_SCROLL_CHANGED event).
   # The EVT_SCROLL_CHANGED event also occurs when using the keyboard to change the thumb position, and when clicking next to the thumb (In all these cases the EVT_SCROLL_THUMBRELEASE event does not happen). In short, the EVT_SCROLL_CHANGED event is triggered when scrolling/ moving has finished independently of the way it had started. Please see the Widgets Sample ("Slider" page) to see the difference between EVT_SCROLL_THUMBRELEASE and EVT_SCROLL_CHANGED in action.
   # 

data/lib/wx/doc/gen/spin_double_event.rb

@@ -26,7 +26,7 @@ module Wx
     #   The constructor.
     #   
     #   Not normally used by the user code.
-    #   @param commandType [Wx::StaticLine::EventType] 
+    #   @param commandType [Wx::Notebook::EventType] 
     #   @param winid [Integer] 
     #   @param value [Float] 
     #   @return [Wx::SpinDoubleEvent]

data/lib/wx/doc/gen/spin_event.rb

@@ -29,7 +29,7 @@ module Wx
   class SpinEvent < NotifyEvent
   
     # The constructor is not normally used by the user code.
-    # @param commandType [Wx::StaticLine::EventType] 
+    # @param commandType [Wx::Notebook::EventType] 
     # @param id [Integer] 
     # @return [Wx::SpinEvent]
     def initialize(commandType=Wx::EVT_NULL, id=0) end

data/lib/wx/doc/gen/splash_screen.rb

@@ -64,7 +64,7 @@ module Wx
     # @return [Wx::SplashScreen]
     def initialize(bitmap, splashStyle, milliseconds, parent, id, pos=Wx::DEFAULT_POSITION, size=Wx::DEFAULT_SIZE, style=(Wx::Border::BORDER_SIMPLE|Wx::FRAME_NO_TASKBAR|Wx::STAY_ON_TOP)) end
     
-    # Returns the splash style (see {splash_screen} for details).
+    # Returns the splash style (see {Wx::SplashScreen#initialize} for details).
     # @return [Integer]
     def get_splash_style; end
     alias_method :splash_style, :get_splash_style

data/lib/wx/doc/gen/splitter_event.rb

@@ -33,7 +33,7 @@ module Wx
     # Constructor.
     # 
     # Used internally by wxWidgets only.
-    # @param eventType [Wx::StaticLine::EventType] 
+    # @param eventType [Wx::Notebook::EventType] 
     # @param splitter [Wx::SplitterWindow] 
     # @return [Wx::SplitterEvent]
     def initialize(eventType=Wx::EVT_NULL, splitter=nil) end

data/lib/wx/doc/gen/stc/styled_text_ctrl.rb

@@ -14,7 +14,6 @@ module Wx::STC
   # Please see {Wx::STC::StyledTextEvent} for the documentation of all event types you can use with {Wx::STC::StyledTextCtrl}.
   # 
   # ## Index of the member groups
-  # 
   # Links for quick access to the various categories of {Wx::STC::StyledTextCtrl} functions:
   # 
   # - Constructors and related methods

data/lib/wx/doc/gen/stc/styled_text_event.rb

@@ -6870,7 +6870,6 @@ module Wx::STC
   # Most of the Scintilla notifications are mapped to a similarly named {Wx::STC::StyledTextEvent}. However a few of the notifications would only offer information available in other wxWidgets event types, and in those cases a corresponding {Wx::STC::StyledTextEvent} is not defined. Currently, the {Wx::EVT_KEY_DOWN} event is used instead of the SCN_KEY notification. The regular wxWidgets drag and drop functionality can be used instead of the SCN_URIDROPPED notification. The {Wx::EVT_SET_FOCUS} event is used instead of the SCN_FOCUSIN notification. And the {Wx::EVT_KILL_FOCUS} event is used instead of the SCN_FOCUSOUT notification.
   # 
   # ## Event Types
-  # 
   # The following is a brief description of when the control generates these events and a list of which methods provide relevant information. Additional details can be found in the Scintilla documentation (http://www.scintilla.org/ScintillaDoc.html\#Notifications).
   # {Wx::STC::EVT_STC_AUTOCOMP_CANCELLED} 
   # 
@@ -7064,7 +7063,7 @@ module Wx::STC
   
     # @overload initialize(commandType=0, id=0)
     #   Constructor.
-    #   @param commandType [Wx::StaticLine::EventType] 
+    #   @param commandType [Wx::Notebook::EventType] 
     #   @param id [Integer] 
     #   @return [Wx::STC::StyledTextEvent]
     # @overload initialize(event)

data/lib/wx/doc/gen/task_bar_icon.rb

@@ -11,7 +11,6 @@ module Wx
   # A taskbar icon is an icon that appears in the 'system tray' and responds to mouse clicks, optionally with a tooltip above it to help provide information.
   # 
   # ## X Window System Note
-  # 
   # Under X Window System, the window manager must support either the "System Tray Protocol" (see http://freedesktop.org/wiki/Specifications/systemtray-spec) by freedesktop.org (WMs used by modern desktop environments such as GNOME >= 2, KDE >= 3 and XFCE >= 4 all do) or the older methods used in GNOME 1.2 and KDE 1 and 2.
   # If it doesn't, the icon will appear as a toplevel window on user's desktop. Because not all window managers have system tray, there's no guarantee that {Wx::TaskBarIcon} will work correctly under X Window System and so the applications should use it only as an optional component of their user interface. The user should be required to explicitly enable the taskbar icon on Unix, it shouldn't be on by default.
   # ### Events emitted by this class

data/lib/wx/doc/gen/task_bar_icon_event.rb

@@ -77,7 +77,7 @@ module Wx
   class TaskBarIconEvent < Event
   
     # Constructor.
-    # @param evtType [Wx::StaticLine::EventType] 
+    # @param evtType [Wx::Notebook::EventType] 
     # @param tbIcon [Wx::TaskBarIcon] 
     # @return [Wx::TaskBarIconEvent]
     def initialize(evtType, tbIcon) end

data/lib/wx/doc/gen/text_ctrl.rb

@@ -524,19 +524,16 @@ module Wx
   # Note that alignment styles ({Wx::TE_LEFT}, {Wx::TE_CENTRE} and {Wx::TE_RIGHT}) can be changed dynamically after control creation on WXMSW, WXGTK and WXOSX. {Wx::TE_READONLY}, {Wx::TE_PASSWORD} and wrapping styles can be dynamically changed under WXGTK but not WXMSW. The other styles can be only set during control creation.
   # 
   # ## wxTextCtrl Text Format
-  # 
   # The multiline text controls always store the text as a sequence of lines separated by <code>'\n'</code> characters, i.e. in the Unix text format even on non-Unix platforms. This allows the user code to ignore the differences between the platforms but at a price: the indices in the control such as those returned by {Wx::TextCtrl#get_insertion_point} or {Wx::TextCtrl#get_selection} can <b>not</b> be used as indices into the string returned by {Wx::TextCtrl#get_value} as they're going to be slightly off for platforms using <code>"\\r\\n"</code> as separator (as Windows does).
   # Instead, if you need to obtain a substring between the 2 indices obtained from the control with the help of the functions mentioned above, you should use {Wx::TextCtrl#get_range}. And the indices themselves can only be passed to other methods, for example {Wx::TextCtrl#set_insertion_point} or {Wx::TextCtrl#set_selection}.
   # To summarize: never use the indices returned by (multiline) {Wx::TextCtrl} as indices into the string it contains, but only as arguments to be passed back to the other {Wx::TextCtrl} methods. This problem doesn't arise for single-line platforms however where the indices in the control do correspond to the positions in the value string.
   # 
   # ## wxTextCtrl Positions and Coordinates
-  # 
   # It is possible to use either linear positions, i.e. roughly (but not always exactly, as explained in the previous section) the index of the character in the text contained in the control or X-Y coordinates, i.e. column and line of the character when working with this class and it provides the functions {Wx::TextCtrl#position_to_xy} and {Wx::TextCtrl#xy_to_position} to convert between the two.
   # Additionally, a position in the control can be converted to its coordinates in pixels using {Wx::TextCtrl#position_to_coords} which can be useful to e.g. show a popup menu near the given character. And, in the other direction, {Wx::TextCtrl#hit_test} can be used to find the character under, or near, the given pixel coordinates.
   # To be more precise, positions actually refer to the gaps between characters and not the characters themselves. Thus, position 0 is the one before the very first character in the control and so is a valid position even when the control is empty. And if the control contains a single character, it has two valid positions: 0 before this character and 1  after it. This, when the documentation of various functions mentions "invalid position", it doesn't consider the position just after the last character of the line to be invalid, only the positions beyond that one (e.g. 2 and greater in the single character example) are actually invalid.
   # 
   # ## wxTextCtrl Styles.
-  # 
   # Multi-line text controls support styling, i.e. provide a possibility to set colours and font for individual characters in it (note that under Windows {Wx::TE_RICH} style is required for style support). To use the styles you can either call {Wx::TextCtrl#set_default_style} before inserting the text or call {Wx::TextCtrl#set_style} later to change the style of the text already in the control (the first solution is much more efficient).
   # In either case, if the style doesn't specify some of the attributes (for example you only want to set the text colour but without changing the font nor the text background), the values of the default style will be used for them. If there is no default style, the attributes of the text control itself are used.
   # So the following code correctly describes what it does: the second call to {Wx::TextCtrl#set_default_style} doesn't change the text foreground colour (which stays red) while the last one doesn't change the background colour (which stays grey):
@@ -551,7 +548,6 @@ module Wx
   # ```
   # 
   # ## wxTextCtrl and C++ Streams
-  # 
   # This class multiply-inherits from std::streambuf (except for some really old compilers using non-standard iostream library), allowing code such as the following:
   # 
   # ```
@@ -604,7 +600,6 @@ module Wx
   # See {Wx::StreamToTextRedirector} for more details.
   # 
   # ## Event Handling.
-  # 
   # The following commands are processed by default event handlers in {Wx::TextCtrl}: {Wx::StandardID::ID_CUT}, {Wx::StandardID::ID_COPY}, {Wx::StandardID::ID_PASTE}, {Wx::StandardID::ID_UNDO}, {Wx::StandardID::ID_REDO}. The associated UI update events are also processed automatically, when the control has the focus.
   # ### Events emitted by this class
   # 

data/lib/wx/doc/gen/text_entry.rb

@@ -371,8 +371,6 @@ module Wx
   # Custom completer objects used with {Wx::TextEntry#auto_complete} must derive from this class and implement its pure virtual method returning the completions. You would typically use a custom completer when the total number of completions is too big for performance to be acceptable if all of them need to be returned at once but if they can be generated hierarchically, i.e. only the first component initially, then the second one after the user finished entering the first one and so on.
   # When inheriting from this class you need to implement its two pure virtual methods. This allows returning the results incrementally and may or not be convenient depending on where do they come from. If you prefer to return all the completions at once, you should inherit from {Wx::TextCompleterSimple} instead.
   # 
-  # 
-  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class TextCompleter < ::Object
   
     # Function called to start iteration over the completions for the given prefix.
@@ -420,8 +418,6 @@ module Wx
   #   text_ctrl.auto_complete(MyTextCompleter.new)
   # ```
   # 
-  # 
-  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class TextCompleterSimple < TextCompleter
   
     # Pure virtual method returning all possible completions for the given prefix.

data/lib/wx/doc/gen/tree_ctrl.rb

@@ -235,13 +235,11 @@ module Wx
   # A similar control with a fully native implementation for GTK+ and macOS as well is {Wx::DataViewTreeCtrl}.
   # 
   # ## Images in wxTreeCtrl
-  # 
   # {Wx::TreeCtrl} inherits from {Wx::WithImages} classes providing the functions for associating images with the control items. Each item refers to its image using an index, which can possibly by {Wx::WithImages::NO_IMAGE} to indicate that the item doesn't use any image at all, and the corresponding image is taken either from the vector passed to {Wx::WithImages#set_images} or from the image list passed to {Wx::WithImages#set_image_list} or {Wx::WithImages#assign_image_list} functions.
   # In addition to normal images, handled with the methods mentioned above, {Wx::TreeCtrl} also provides optional state images that may be used to indicate some additional state of the item, e.g. checked or unchecked status. These images can be set using {Wx::TreeCtrl#set_state_image_list} and {Wx::TreeCtrl#assign_state_image_list} functions that behave in the same way as the corresponding methods of {Wx::WithImages}.
   # Finally, in the generic version of this control ({Wx::GenericTreeCtrl}), also provides {Wx::TreeCtrl#set_buttons_image_list} and {Wx::TreeCtrl#assign_buttons_image_list}, which can be used to change the images used for the control buttons, used to expand or collapse its branches. These methods are not available in the native WXMSW and {Wx::Qt} implementations.
   # 
   # ## Events
-  # 
   # To intercept events from a tree control, use the event table macros described in {Wx::TreeEvent}.
   # ### Styles
   # 

data/lib/wx/doc/gen/tree_event.rb

@@ -64,7 +64,7 @@ module Wx
   class TreeEvent < NotifyEvent
   
     # Constructor, used by wxWidgets itself only.
-    # @param commandType [Wx::StaticLine::EventType] 
+    # @param commandType [Wx::Notebook::EventType] 
     # @param tree [Wx::TreeCtrl] 
     # @param item [Wx::TreeItemId] 
     # @return [Wx::TreeEvent]

data/lib/wx/doc/gen/utils.rb

@@ -57,8 +57,6 @@ module Wx
   # <p>This function is categorized as a GUI one and so is not thread-safe.
   # </p>
   # </div>
-  # 
-  # Include file: \#include <wx/utils.h>
   # @return [void]
   def self.bell; end
   
@@ -150,8 +148,6 @@ module Wx
   # <p>For some configurations of the running user, the application which is launched to open the given URL may be URL-dependent (e.g. a browser may be used for local URLs while another one may be used for remote URLs).
   # </p>
   # </div>
-  # 
-  # Include file: \#include <wx/utils.h>
   # @see launch_default_application
   # @see  execute
   # @param url [String] 
@@ -171,8 +167,6 @@ module Wx
   # Copies the user's email address into the supplied buffer, by concatenating the values returned by {get_full_host_name} and {get_user_id}.
   # 
   # true if successful, false otherwise.
-  # 
-  # Include file: \#include <wx/utils.h>
   # @return [String]
   def self.get_email_address; end
   
@@ -192,8 +186,6 @@ module Wx
   # 
   # Please note that the returned name is not fully qualified, i.e. it does not include the domain name.
   # The hostname if successful or an empty string otherwise.
-  # 
-  # Include file: \#include <wx/utils.h>
   # @see get_full_host_name
   # @return [String]
   def self.get_host_name; end
@@ -217,8 +209,6 @@ module Wx
   # 
   # something like "jsmith"). It uniquely identifies the current user (on this system). Under Windows or NT, this function first looks in the environment variables USER and LOGNAME; if neither of these is found, the entry <b>UserId</b> in the <b>wxWidgets</b> section of the WIN.INI file is tried.
   # The login name if successful or an empty string otherwise.
-  # 
-  # Include file: \#include <wx/utils.h>
   # @see get_user_name
   # @return [String]
   def self.get_user_id; end
@@ -227,8 +217,6 @@ module Wx
   # 
   # Under Windows or NT, this function looks for the entry UserName in the wxWidgets section of the WIN.INI file. If PenWindows is running, the entry Current in the section User of the PENWIN.INI file is used.
   # The full user name if successful or an empty string otherwise.
-  # 
-  # Include file: \#include <wx/utils.h>
   # @see get_user_id
   # @return [String]
   def self.get_user_name; end
@@ -260,8 +248,6 @@ module Wx
   # <p>This function is not 100% reliable on some systems given the fact that there isn't always a standard way to do a reliable check on the OS bitness.
   # </p>
   # </div>
-  # 
-  # Include file: \#include <wx/utils.h>
   # @return [Boolean]
   def self.is_platform64bit; end
   
@@ -303,8 +289,6 @@ module Wx
   # </div>
   # 
   # true on success, false if an error occurred.
-  # 
-  # Include file: \#include <wx/utils.h>
   # @param flags [Integer]  One of {Wx::SHUTDOWN_POWEROFF}, {Wx::SHUTDOWN_REBOOT} or {Wx::SHUTDOWN_LOGOFF} (currently implemented only for MSW) possibly combined with {Wx::SHUTDOWN_FORCE} which forces shutdown under MSW by forcefully terminating all the applications. As doing this can result in a data loss, this flag shouldn't be used unless really necessary.
   # @return [Boolean]
   def self.shutdown(flags=Wx::SHUTDOWN_POWEROFF) end

data/lib/wx/doc/gen/v_scrolled_window.rb

@@ -12,7 +12,6 @@ module Wx
   # To use this class, you need to derive from it and implement the {Wx::VScrolledWindow#on_get_row_height} pure virtual method. You also must call {Wx::VScrolledWindow#set_row_count} to let the base class know how many rows it should display, but from that moment on the scrolling is handled entirely by {Wx::VScrolledWindow}. You only need to draw the visible part of contents in your <code>OnPaint()</code> method as usual. You should use {Wx::VScrolledWindow#get_visible_rows_begin} and {Wx::VScrolledWindow#get_visible_rows_end} to select the lines to display. Note that the device context origin is not shifted so the first visible row always appears at the point (0, 0) in physical as well as logical coordinates.
   # 
   # ## wxWidgets 2.8 Compatibility Functions
-  # 
   # The following functions provide backwards compatibility for applications originally built using {Wx::VScrolledWindow} in 2.6 or 2.8. Originally, {Wx::VScrolledWindow} referred to scrolling "lines". We now use "units" in {Wx::VarScrollHelperBase} to avoid implying any orientation (since the functions are used for both horizontal and vertical scrolling in derived classes). And in the new {Wx::VScrolledWindow} and {Wx::HScrolledWindow} classes, we refer to them as "rows" and "columns", respectively. This is to help clear some confusion in not only those classes, but also in {Wx::HVScrolledWindow} where functions are inherited from both.
   # You are encouraged to update any existing code using these function to use the new replacements mentioned below, and avoid using these functions for any new code as they are deprecated.
   # 

data/lib/wx/doc/gen/wizard.rb

@@ -33,7 +33,6 @@ module Wx
   # - {Wx::EvtHandler#evt_wizard_finished}(id, meth = nil, &block): The wizard finished button was pressed. 
   # 
   # ## Extended styles
-  # 
   # Use the {Wx::Window#set_extra_style} function to set the following style. You will need to use two-step construction (use the default constructor, call {Wx::Wizard#set_extra_style}, then call Create).
   # 
   # ### Extra Styles

data/lib/wx/doc/gen/wizard_event.rb

@@ -90,7 +90,7 @@ module Wx
     # Constructor.
     # 
     # It is not normally used by the user code as the objects of this type are constructed by {Wx::Wizard}.
-    # @param type [Wx::StaticLine::EventType] 
+    # @param type [Wx::Notebook::EventType] 
     # @param id [Integer] 
     # @param direction [Boolean] 
     # @param page [Wx::WizardPage] 

data/lib/wx/doc/gen/wizard_page.rb

@@ -12,7 +12,6 @@ module Wx
   # This class allows the programmer to decide the order of pages in the wizard dynamically (during run-time) and so provides maximal flexibility. Usually, however, the order of pages is known in advance in which case {Wx::WizardPageSimple} class is enough and it is simpler to use.
   # 
   # ## Virtual functions to override
-  # 
   # To use this class, you must override {Wx::WizardPage#get_prev} and {Wx::WizardPage#get_next} pure virtual functions (or you may use {Wx::WizardPageSimple} instead). {Wx::WizardPage#get_bitmap} can also be overridden, but this should be very rarely needed.
   # 
   # Category:  Miscellaneous Windows

data/lib/wx/doc/owner_drawn_combobox.rb

@@ -7,7 +7,11 @@
 
 module Wx
 
-  class OwnerDrawnComboBox
+  class OwnerDrawnComboBox < ComboCtrl
+
+    alias :get_item_data :get_client_object
+
+    alias :set_item_data :set_client_object
 
     # Returns the label of the selected item or an empty string if no item is selected.
     #