wxruby3 0.9.4-x64-mingw-ucrt → 0.9.5-x64-mingw-ucrt

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

@@ -10,67 +10,59 @@ module Wx
   # 
   # {Wx::FileDialogCustomizeHook} is an abstract base class, i.e. in order to use a concrete class inheriting from it and implementing its pure virtual {Wx::FileDialogCustomizeHook#add_custom_controls} function must be defined. Then an object of this class should be passed to {Wx::FileDialog#set_customize_hook}, which will result in its {Wx::FileDialogCustomizeHook#add_custom_controls} being called before the dialog is shown, {Wx::FileDialogCustomizeHook#update_custom_controls} being called whenever something changes in the dialog while it is shown and, finally, {Wx::FileDialogCustomizeHook#transfer_data_from_custom_controls} being called when the user accepts their choice in the dialog.
   # Putting all this together, here is an example of customizing the file dialog using this class: 
-  # ```
-  #   class EncryptHook : public wxFileDialogCustomizeHook
-  #   {
-  #   public:
-  #       // Override to add custom controls using the provided customizer object.
-  #       void AddCustomControls(wxFileDialogCustomize& customizer) override
-  #       {
-  #           // Suppose we can encrypt files when saving them.
-  #           m_checkbox = customizer.AddCheckBox("Encrypt");
-  #   
-  #           // While m_checkbox is not a wxCheckBox, it looks almost like one
-  #           // and, in particular, we can bind to custom control events as usual.
-  #           m_checkbox->Bind(wxEVT_CHECKBOX, [this](wxCommandEvent& event) {
-  #               // We can also call wxWindow-like functions on them.
-  #               m_button->Enable(event.IsChecked());
-  #           });
-  #   
-  #           // The encryption parameters can be edited in a dedicated dialog.
-  #           m_button = customizer.AddButton("Parameters...");
-  #           m_button->Bind(wxEVT_BUTTON, [](wxCommandEvent&) {
-  #               ... show the encryption parameters dialog here ...
-  #           });
-  #       }
-  #   
-  #       // Override to save the values of the custom controls.
-  #       void TransferDataFromCustomControls() override
-  #       {
-  #           // Save the checkbox value, as we won't be able to use it any more
-  #           // once this function returns.
-  #           m_encrypt = m_checkbox->GetValue();
-  #       }
-  #   
-  #       // Just a simple accessor to get the results.
-  #       bool Encrypt() const { return m_encrypt; }
-  #   
-  #   private:
-  #       wxFileDialogButton* m_button;
-  #       wxFileDialogCheckBox* m_checkbox;
-  #   
-  #       bool m_encrypt = false;
-  #   };
-  #   
-  #   void SomeFunc()
-  #   {
-  #       wxFileDialog dialog(NULL, "Save document", wxString(), "file.my",
-  #                           "My files (*.my)|*.my",
-  #                           wxFD_SAVE | wxFD_OVERWRITE_PROMPT);
-  #   
-  #       // This object may be destroyed before the dialog, but must remain
-  #       // alive until ShowModal() returns.
-  #       EncryptHook customizeHook;
-  #       dialog.SetCustomizeHook(customHook);
-  #   
-  #       if ( dialog.ShowModal() == wxID_OK )
-  #       {
-  #           if ( customizeHook.Encrypt() )
-  #               ... save with encryption ...
-  #           else
-  #               ... save without encryption ...
-  #       }
-  #   }
+  # ```ruby
+  # class EncryptHook < Wx::FileDialogCustomizeHook
+  # 
+  #   attr_reader :encrypt
+  # 
+  #   # Override to add custom controls using the provided customizer object.
+  #   def add_custom_controls(customizer)
+  #     # Suppose we can encrypt files when saving them.
+  #     @checkbox = customizer.add_check_box('Encrypt')
+  # 
+  #     # While @checkbox is not a Wx::CheckBox, it looks almost like one
+  #     # and, in particular, we can bind to custom control events as usual.
+  #     @checkbox.evt_checkbox(Wx::ID_ANY) do |event| 
+  #        # We can also call Wx::Window-like functions on them.
+  #        @button.enable(event.checked?)
+  #     end
+  # 
+  #     # The encryption parameters can be edited in a dedicated dialog.
+  #     @button = customizer.add_button('Parameters...')
+  #     @button.evt_button(Wx::ID_ANY) do |event|
+  #        # ... show the encryption parameters dialog here ...
+  #     end
+  #   end
+  # 
+  #   # Override to save the values of the custom controls.
+  #   def transfer_data_from_custom_controls 
+  #     # Save the checkbox value, as we won't be able to use it any more
+  #     # once this function returns.
+  #     @encrypt = @checkbox.get_value
+  #   end
+  # 
+  # end
+  # 
+  # # ...
+  # 
+  # def some_method
+  #   Wx.FileDialog(nil, 'Save document', '', 'file.my',
+  #                      'My files (*.my)|*.my',
+  #                      Wx::FD_SAVE | Wx::FD_OVERWRITE_PROMPT) do |dialog|
+  # 
+  #     # This object may be destroyed before the dialog, but must remain
+  #     # alive until #show_modal returns.
+  #     customize_hook = EncryptHook.new
+  #     dialog.set_customize_hook(custom_hook)
+  # 
+  #     if dialog.show_modal == Wx::ID_OK 
+  #       if customize_hook.encrypt 
+  #         # ... save with encryption ...
+  #       else
+  #         # ... save without encryption ...
+  #       end
+  #     end
+  # end
   # ```
   # 
   # Category:  Common Dialogs

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

@@ -91,14 +91,7 @@ module Wx
     
     # Returns true if the handler is able to open this file.
     # 
-    # This function doesn't check whether the file exists or not, it only checks if it knows the protocol. Example:
-    # 
-    # ```
-    #   bool MyHand::CanOpen(const wxString& location)
-    #   {
-    #       return (GetProtocol(location) == "http");
-    #   }
-    # ```
+    # This function doesn't check whether the file exists or not, it only checks if it knows the protocol. 
     # 
     # Must be overridden in derived handlers.
     # @param location [String] 
@@ -132,10 +125,6 @@ module Wx
     # Returns the MIME type based on <b>extension</b> of location.
     # 
     # (While {Wx::FSFile#get_mime_type} returns real MIME type - either extension-based or queried from HTTP.)
-    # Example: 
-    # ```
-    #   GetMimeTypeFromExt("index.htm") == "text/html"
-    # ```
     # @param location [String] 
     # @return [String]
     def self.get_mime_type_from_ext(location) end
@@ -161,52 +150,6 @@ module Wx
   # 
   # It is particularly suitable for storing bitmaps from resources or included XPM files so that they can be used with {Wx::HTML} or {Wx::WebView}.
   # Filenames are prefixed with <code>"memory:"</code>, e.g. <code>"memory:myfile.html"</code>.
-  # Example:
-  # 
-  # ```
-  #   \#ifndef __WXMSW__
-  #   \#include "logo.xpm"
-  #   \#endif
-  #   
-  #   void MyFrame::OnAbout(wxCommandEvent&)
-  #   {
-  #       wxFileSystem::AddHandler(new wxMemoryFSHandler);
-  #       wxMemoryFSHandler::AddFile("logo.png", wxBITMAP(logo), wxBITMAP_TYPE_PNG);
-  #       wxMemoryFSHandler::AddFile("about.htm",
-  #                               "<html><body>About: "
-  #                               "<img src=\"memory:logo.png\"></body></html>");
-  #   
-  #       wxDialog dlg(this, -1, wxString(_("About")));
-  #       wxBoxSizer *topsizer;
-  #       topsizer = new wxBoxSizer(wxVERTICAL);
-  #   \#ifdef USE_WEBVIEW
-  #       wxWebView* browser = wxWebView::New(&dlg, wxID_ANY, wxWebViewDefaultURLStr,
-  #                                wxDefaultPosition, wxSize(380, 160));
-  #       browser->RegisterHandler(wxSharedPtr<wxWebViewHandler>(new wxWebViewFSHandler("memory")));
-  #       browser->LoadURL("memory:about.htm");
-  #   \#else // Use wxHtml
-  #       wxHtmlWindow *browser;
-  #       browser = new wxHtmlWindow(&dlg, -1, wxDefaultPosition,
-  #                                  wxSize(380, 160), wxHW_SCROLLBAR_NEVER);
-  #       browser->SetBorders(0);
-  #       browser->LoadPage("memory:about.htm");
-  #       browser->SetSize(browser->GetInternalRepresentation()->GetWidth(),
-  #                   browser->GetInternalRepresentation()->GetHeight());
-  #   \#endif
-  #       topsizer->Add(browser, 1, wxALL, 10);
-  #       topsizer->Add(new wxStaticLine(&dlg, -1), 0, wxEXPAND | wxLEFT | wxRIGHT, 10);
-  #       topsizer->Add(new wxButton(&dlg, wxID_OK, "Ok"),
-  #                   0, wxALL | wxALIGN_RIGHT, 15);
-  #       dlg.SetAutoLayout(true);
-  #       dlg.SetSizer(topsizer);
-  #       topsizer->Fit(&dlg);
-  #       dlg.Centre();
-  #       dlg.ShowModal();
-  #   
-  #       wxMemoryFSHandler::RemoveFile("logo.png");
-  #       wxMemoryFSHandler::RemoveFile("about.htm");
-  #   }
-  # ```
   # 
   # Category:  Virtual File System
   # @see Wx::MemoryFSHandler.add_file_with_mime_type 

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

@@ -28,7 +28,6 @@ module Wx
   # </div>
   # 
   # ## Default event processing
-  # 
   # {Wx::Frame} processes the following events:
   # 
   # - {Wx::EVT_SIZE}: if the frame has exactly one child window, not counting the status and toolbar, this child is resized to take the entire frame client area. If two or more windows are present, they should be laid out explicitly either by manually handling {Wx::EVT_SIZE} or using sizers; 

data/lib/wx/doc/gen/grid/grid_ctrl.rb

@@ -273,18 +273,6 @@ module Wx::GRID
     # @wxrb_require USE_GRID
     class CellSpan < Wx::Enum
     
-      # This cell is inside a span covered by another cell.
-      # 
-      CellSpan_Inside = Wx::GRID::Grid::CellSpan.new(-1)
-      
-      # This is a normal, non-spanning cell.
-      # 
-      CellSpan_None = Wx::GRID::Grid::CellSpan.new(0)
-      
-      # This cell spans several physical {Wx::GRID::Grid} cells.
-      # 
-      CellSpan_Main = Wx::GRID::Grid::CellSpan.new(1)
-      
     end # CellSpan
     
     # Constants defining different support built-in TAB handling behaviours.

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

@@ -62,7 +62,6 @@ module Wx
   # This control is implemented using the native header control under MSW systems and a generic implementation elsewhere.
   # 
   # ## Future Improvements
-  # 
   # Some features are supported by the native MSW control and so could be easily implemented in this version of {Wx::HeaderCtrl} but need to be implemented in the generic version as well to be really useful. Please let us know if you need or, better, plan to work on implementing, any of them:
   # 
   # - Displaying bitmaps instead of or together with the text

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

@@ -253,13 +253,11 @@ module Wx
   # One colour value of the image may be used as a mask colour which will lead to the automatic creation of a {Wx::Mask} object associated to the bitmap object.
   # 
   # ## Alpha channel support
-  # 
   # Starting from wxWidgets 2.5.0 {Wx::Image} supports alpha channel data, that is in addition to a byte for the red, green and blue colour components for each pixel it also stores a byte representing the pixel opacity.
   # An alpha value of 0 corresponds to a transparent pixel (null opacity) while a value of 255 means that the pixel is 100% opaque. The constants {Wx::IMAGE_ALPHA_TRANSPARENT} and {Wx::IMAGE_ALPHA_OPAQUE} can be used to indicate those values in a more readable form.
   # While all images have RGB data, not all images have an alpha channel. Before using {Wx::Image#get_alpha} you should check if this image contains an alpha channel with {Wx::Image#has_alpha}. Currently the BMP, PNG, TGA, and TIFF format handlers have full alpha channel support for loading so if you want to use alpha you have to use one of these formats. If you initialize the image alpha channel yourself using {Wx::Image#set_alpha}, you should save it in either PNG, TGA, or TIFF format to avoid losing it as these are the only handlers that currently support saving with alpha.
   # 
   # ## Available image handlers
-  # 
   # The following image handlers are available. {Wx::BMPHandler} is always installed by default. In wxRuby all image handlers are loaded by default at startup by {init_all_image_handlers}.
   # 
   # - {Wx::BMPHandler}: For loading (including alpha support) and saving, always installed.

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

@@ -329,7 +329,6 @@ module Wx
   # </div>
   # 
   # ## Column Ordering
-  # 
   # By default, the columns of a list control appear on the screen in order of their indices, i.e. column 0 appears first, then column 1 next, and so on. However this can be changed by using the {Wx::ListCtrl#set_columns_order} function to arbitrarily reorder the columns visual order.
   # The user can also rearrange the columns interactively by dragging them. In this case, the index of the column is not the same as its order and the functions {Wx::ListCtrl#get_column_order} and {Wx::ListCtrl#get_column_index_from_order} should be used to translate between them.
   # 

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

@@ -11,13 +11,11 @@ module Wx
   # {Wx::MediaCtrl} uses native backends to render media, for example on Windows there is a ActiveMovie/DirectShow backend, and on Macintosh there is a QuickTime backend.
   # 
   # ## Rendering media
-  # 
   # Depending upon the backend, {Wx::MediaCtrl} can render and display pretty much any kind of media that the native system can - such as an image, mpeg video, or mp3 (without license restrictions - since it relies on native system calls that may not technically have mp3 decoding available, for example, it falls outside the realm of licensing restrictions).
   # For general operation, all you need to do is call {Wx::MediaCtrl#load} to load the file you want to render, catch the EVT_MEDIA_LOADED event, and then call {Wx::MediaCtrl#play} to show the video/audio of the media in that event.
   # More complex operations are generally more heavily dependent on the capabilities of the backend. For example, QuickTime cannot set the playback rate of certain streaming media - while DirectShow is slightly more flexible in that regard.
   # 
   # ## Operation
-  # 
   # When {Wx::MediaCtrl} plays a file, it plays until the stop position is reached (currently the end of the file/stream). Right before it hits the end of the stream, it fires off a EVT_MEDIA_STOP event to its parent window, at which point the event handler can choose to veto the event, preventing the stream from actually stopping.
   # Example:
   # 
@@ -40,16 +38,13 @@ module Wx
   # Note that when changing the state of the media through {Wx::MediaCtrl#play} and other methods, the media may not actually be in the {Wx::MediaState::MEDIASTATE_PLAYING}, for example. If you are relying on the media being in certain state, catch the event relevant to the state. See {Wx::MediaEvent} for the kinds of events that you can catch.
   # 
   # ## Video size
-  # 
   # By default, {Wx::MediaCtrl} will scale the size of the video to the requested amount passed to either its constructor or {Wx::MediaCtrl#create}. After calling {Wx::MediaCtrl#load} or performing an equivalent operation, you can subsequently obtain the "real" size of the video (if there is any) by calling {Wx::MediaCtrl#get_best_size}. Note that the actual result on the display will be slightly different when {Wx::MediaCtrl#show_player_controls} is activated and the actual video size will be less than specified due to the extra controls provided by the native toolkit. In addition, the backend may modify {Wx::MediaCtrl#get_best_size} to include the size of the extra controls - so if you want the real size of the video just disable {Wx::MediaCtrl#show_player_controls}.
   # The idea with setting {Wx::MediaCtrl#get_best_size} to the size of the video is that {Wx::MediaCtrl#get_best_size} is a {Wx::Window}-derived function that is called when sizers on a window recalculate. What this means is that if you use sizers by default the video will show in its original size without any extra assistance needed from the user.
   # 
   # ## Player controls
-  # 
   # Normally, when you use {Wx::MediaCtrl} it is just a window for the video to play in. However, some toolkits have their own media player interface. For example, QuickTime generally has a bar below the video with a slider. A special feature available to {Wx::MediaCtrl}, you can use the toolkits interface instead of making your own by using the {Wx::MediaCtrl#show_player_controls} function. There are several options for the flags parameter, with the two general flags being {Wx::MediaCtrlPlayerControls::MEDIACTRLPLAYERCONTROLS_NONE} which turns off the native interface, and {Wx::MediaCtrlPlayerControls::MEDIACTRLPLAYERCONTROLS_DEFAULT} which lets {Wx::MediaCtrl} decide what native controls on the interface. Be sure to review the caveats outlined in Video size before doing so.
   # 
   # ## Choosing a backend
-  # 
   # Generally, you should almost certainly leave this part up to {Wx::MediaCtrl} - but if you need a certain backend for a particular reason, such as QuickTime for playing .mov files, all you need to do to choose a specific backend is to pass the name of the backend class to {Wx::MediaCtrl#create}.
   # The following are valid backend identifiers:
   # 
@@ -59,7 +54,6 @@ module Wx
   # - <b>{Wx::MEDIABACKEND_WMP10}</b>, Use Windows Media Player 10 (Windows only). Works on systems with either Windows Media Player 9 or 10 installed.
   # 
   # ## Creating a backend
-  # 
   # Creating a backend for {Wx::MediaCtrl} is a rather simple process. Simply derive from {Wx::MediaBackendCommonBase} and implement the methods you want. The methods in {Wx::MediaBackend} correspond to those in {Wx::MediaCtrl} except for {Wx::MediaCtrl::CreateControl} which does the actual creation of the control, in cases where a custom control is not needed you may simply call {Wx::Control#create}.
   # You need to make sure to use the {Wx::DECLARE_CLASS} and {Wx::IMPLEMENT_CLASS} macros.
   # The only real tricky part is that you need to make sure the file in compiled in, which if there are just backends in there will not happen and you may need to use a force link hack (see {Wx::FORCE_LINK_MODULE} usage in the mediactrl sample).

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

@@ -21,12 +21,10 @@ module Wx
   # The radio items are similar to the check items except that all the other items in the same radio group are unchecked when a radio item is checked. The radio group is formed by a contiguous range of radio items, i.e. it starts at the first item of this kind and ends with the first item of a different kind (or the end of the menu). Notice that because the radio groups are defined in terms of the item positions inserting or removing the items in the menu containing the radio items risks to not work correctly.
   # 
   # ## Allocation strategy
-  # 
   # All menus must be created on the <b>heap</b> because all menus attached to a menubar or to another menu will be deleted by their parent when it is deleted. The only exception to this rule are the popup menus (i.e. menus used with {Wx::Window#popup_menu}) as wxWidgets does not destroy them to allow reusing the same menu more than once. But the exception applies only to the menus themselves and not to any submenus of popup menus which are still destroyed by wxWidgets as usual and so must be heap-allocated.
   # As the frame menubar is deleted by the frame itself, it means that normally all menus used are deleted automatically.
   # 
   # ## Event handling
-  # 
   # Event handlers for the commands generated by the menu items can be connected directly to the menu object itself using {Wx::EvtHandler#bind}. If this menu is a submenu of another one, the events from its items can also be processed in the parent menu and so on, recursively.
   # If the menu is part of a menu bar, then events can also be handled in {Wx::MenuBar} object.
   # Finally, menu events can also be handled in the associated window, which is either the {Wx::Frame} associated with the menu bar this menu belongs to or the window for which {Wx::Window#popup_menu} was called for the popup menus.

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

@@ -91,7 +91,6 @@ module Wx
   # - {Wx::EvtHandler#evt_notebook_page_changing}(id, meth = nil, &block): The page selection is about to be changed. Processes a {Wx::EVT_NOTEBOOK_PAGE_CHANGING} event. This event can be vetoed. 
   # 
   # ## Page backgrounds
-  # 
   # On Windows, the default theme paints a background on the notebook's pages. If you wish to suppress this theme, for aesthetic or performance reasons, there are three ways of doing it. You can use {Wx::NB_NOPAGETHEME} to disable themed drawing for a particular notebook, you can call {Wx::SystemOptions.set_option} to disable it for the whole application, or you can disable it for individual pages by using {Wx::Notebook#set_background_colour}.
   # To disable themed pages globally: 
   # ```ruby

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_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::PropertyGrid::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::PropertyGrid::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/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/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/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} 
   # 

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