wxruby3 0.9.0.pre.beta.13-x64-mingw-ucrt → 0.9.0.pre.rc.1-x64-mingw-ucrt

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

@@ -212,19 +212,21 @@ module Wx
     # The label string for the normal menu items (not separators) may include the accelerator which can be used to activate the menu item from keyboard. An accelerator key can be specified using the ampersand <code>&</code> character. In order to embed an ampersand character in the menu item text, the ampersand must be doubled.
     # Optionally you can specify also an accelerator string appending a tab character <code>\t</code> followed by a valid key combination (e.g. <code>CTRL+V</code>). Its general syntax is any combination of <code>"CTRL"</code>, <code>"RAWCTRL"</code>, <code>"ALT"</code> and <code>"SHIFT"</code> strings (case doesn't matter) separated by either <code>'-'</code> or <code>'+'</code> characters and followed by the accelerator itself. Notice that CTRL corresponds to the "Ctrl" key on most platforms but not under macOS where it is mapped to "Cmd" key on Mac keyboard. Usually this is exactly what you want in portable code but if you really need to use the (rarely used for this purpose) "Ctrl" key even under Mac, you may use RAWCTRL to prevent this mapping. Under the other platforms RAWCTRL is the same as plain CTRL.
     # The accelerator may be any alphanumeric character, any function key (from F1 to F12), any numpad digit key using KP_ prefix (i.e. from KP_0 to KP_9) or one of the special strings listed below (again, case doesn't matter) corresponding to the specified key code:
-    # - Del or Delete: WXK_DELETE- Back: WXK_BACK- Ins or Insert: WXK_INSERT- Enter or Return: WXK_RETURN- PgUp or PageUp: WXK_PAGEUP- PgDn or PageDown: WXK_PAGEDOWN- Left: WXK_LEFT- Right: WXK_RIGHT- Up: WXK_UP- Down: WXK_DOWN- Home: WXK_HOME- End: WXK_END- Space: WXK_SPACE- Tab: WXK_TAB- Esc or Escape: WXK_ESCAPE- Cancel: WXK_CANCEL- Clear: WXK_CLEAR- Menu: WXK_MENU- Pause: WXK_PAUSE- Capital: WXK_CAPITAL- Select: WXK_SELECT- Print: WXK_PRINT- Execute: WXK_EXECUTE- Snapshot: WXK_SNAPSHOT- Help: WXK_HELP- Add: WXK_ADD- Separator: WXK_SEPARATOR- Subtract: WXK_SUBTRACT- Decimal: WXK_DECIMAL- Divide: WXK_DIVIDE- Num_lock: WXK_NUMLOCK- Scroll_lock: WXK_SCROLL- KP_Space: WXK_NUMPAD_SPACE- KP_Tab: WXK_NUMPAD_TAB- KP_Enter: WXK_NUMPAD_ENTER- KP_Home: WXK_NUMPAD_HOME- KP_Left: WXK_NUMPAD_LEFT- KP_Up: WXK_NUMPAD_UP- KP_Right: WXK_NUMPAD_RIGHT- KP_Down: WXK_NUMPAD_DOWN- KP_PageUp: WXK_NUMPAD_PAGEUP- KP_PageDown: WXK_NUMPAD_PAGEDOWN- KP_Prior: WXK_NUMPAD_PAGEUP- KP_Next: WXK_NUMPAD_PAGEDOWN- KP_End: WXK_NUMPAD_END- KP_Begin: WXK_NUMPAD_BEGIN- KP_Insert: WXK_NUMPAD_INSERT- KP_Delete: WXK_NUMPAD_DELETE- KP_Equal: WXK_NUMPAD_EQUAL- KP_Multiply: WXK_NUMPAD_MULTIPLY- KP_Add: WXK_NUMPAD_ADD- KP_Separator: WXK_NUMPAD_SEPARATOR- KP_Subtract: WXK_NUMPAD_SUBTRACT- KP_Decimal: WXK_NUMPAD_DECIMAL- KP_Divide: WXK_NUMPAD_DIVIDE- Windows_Left: WXK_WINDOWS_LEFT- Windows_Right: WXK_WINDOWS_RIGHT- Windows_Menu: WXK_WINDOWS_MENU- Command: WXK_COMMAND
+    # - Del or Delete: {Wx::K_DELETE}- Back: {Wx::K_BACK}- Ins or Insert: {Wx::K_INSERT}- Enter or Return: {Wx::K_RETURN}- PgUp or PageUp: {Wx::K_PAGEUP}- PgDn or PageDown: {Wx::K_PAGEDOWN}- Left: {Wx::K_LEFT}- Right: {Wx::K_RIGHT}- Up: {Wx::K_UP}- Down: {Wx::K_DOWN}- Home: {Wx::K_HOME}- End: {Wx::K_END}- Space: {Wx::K_SPACE}- Tab: {Wx::K_TAB}- Esc or Escape: {Wx::K_ESCAPE}- Cancel: {Wx::K_CANCEL}- Clear: {Wx::K_CLEAR}- Menu: {Wx::K_MENU}- Pause: {Wx::K_PAUSE}- Capital: {Wx::K_CAPITAL}- Select: {Wx::K_SELECT}- Print: {Wx::K_PRINT}- Execute: {Wx::K_EXECUTE}- Snapshot: {Wx::K_SNAPSHOT}- Help: {Wx::K_HELP}- Add: {Wx::K_ADD}- Separator: {Wx::K_SEPARATOR}- Subtract: {Wx::K_SUBTRACT}- Decimal: {Wx::K_DECIMAL}- Divide: {Wx::K_DIVIDE}- Num_lock: {Wx::K_NUMLOCK}- Scroll_lock: {Wx::K_SCROLL}- KP_Space: {Wx::K_NUMPAD}_SPACE- KP_Tab: {Wx::K_NUMPAD}_TAB- KP_Enter: {Wx::K_NUMPAD}_ENTER- KP_Home: {Wx::K_NUMPAD}_HOME- KP_Left: {Wx::K_NUMPAD}_LEFT- KP_Up: {Wx::K_NUMPAD}_UP- KP_Right: {Wx::K_NUMPAD}_RIGHT- KP_Down: {Wx::K_NUMPAD}_DOWN- KP_PageUp: {Wx::K_NUMPAD}_PAGEUP- KP_PageDown: {Wx::K_NUMPAD}_PAGEDOWN- KP_Prior: {Wx::K_NUMPAD}_PAGEUP- KP_Next: {Wx::K_NUMPAD}_PAGEDOWN- KP_End: {Wx::K_NUMPAD}_END- KP_Begin: {Wx::K_NUMPAD}_BEGIN- KP_Insert: {Wx::K_NUMPAD}_INSERT- KP_Delete: {Wx::K_NUMPAD}_DELETE- KP_Equal: {Wx::K_NUMPAD}_EQUAL- KP_Multiply: {Wx::K_NUMPAD}_MULTIPLY- KP_Add: {Wx::K_NUMPAD}_ADD- KP_Separator: {Wx::K_NUMPAD}_SEPARATOR- KP_Subtract: {Wx::K_NUMPAD}_SUBTRACT- KP_Decimal: {Wx::K_NUMPAD}_DECIMAL- KP_Divide: {Wx::K_NUMPAD}_DIVIDE- Windows_Left: {Wx::K_WINDOWS}_LEFT- Windows_Right: {Wx::K_WINDOWS}_RIGHT- Windows_Menu: {Wx::K_WINDOWS}_MENU- Command: {Wx::K_COMMAND}
     # 
     # Examples:
     # 
+    # ```
     #   m_pMyMenuItem->SetItemLabel("My &item\tCTRL+I");
     #   m_pMyMenuItem2->SetItemLabel("Clean && build\tF7");
     #   m_pMyMenuItem3->SetItemLabel("Simple item");
     #   m_pMyMenuItem4->SetItemLabel("Item with &accelerator");
+    # ```
     # 
     # In {Wx::GTK} using <code>"SHIFT"</code> with non-alphabetic characters currently doesn't work, even in combination with other modifiers, due to GTK+ limitation. E.g. <code>Shift+Ctrl+A</code> works but <code>Shift+Ctrl+1</code> or <code>Shift+/</code> do not, so avoid using accelerators of this form in portable code.
     # 
     # In {Wx::GTk}, the left/right/up/down arrow keys do not work as accelerator keys for a menu item unless a modifier key is used. Additionally, the following keycodes are not supported as menu accelerator keys:
-    # - WXK_COMMAND/WXK_CONTROL- WXK_SHIFT- WXK_ALT- WXK_SCROLL- WXK_CAPITAL- WXK_NUMLOCK- WXK_NUMPAD_TAB- WXK_TAB- WXK_WINDOWS_LEFT- WXK_WINDOWS_RIGHT- WXK_ADD- WXK_SEPARATOR- WXK_SUBTRACT- WXK_DECIMAL- WXK_DIVIDE- WXK_SNAPSHOT
+    # - {Wx::K_COMMAND}/{Wx::K_CONTROL}- {Wx::K_SHIFT}- {Wx::K_ALT}- {Wx::K_SCROLL}- {Wx::K_CAPITAL}- {Wx::K_NUMLOCK}- {Wx::K_NUMPAD}_TAB- {Wx::K_TAB}- {Wx::K_WINDOWS}_LEFT- {Wx::K_WINDOWS}_RIGHT- {Wx::K_ADD}- {Wx::K_SEPARATOR}- {Wx::K_SUBTRACT}- {Wx::K_DECIMAL}- {Wx::K_DIVIDE}- {Wx::K_SNAPSHOT}
     # @see Wx::MenuItem#get_item_label
     # @see  Wx::MenuItem#get_item_label_text 
     # @param label [String] 
@@ -266,7 +268,7 @@ module Wx
     
     # Add an extra accelerator for this menu item.
     # Additional accelerators are not shown in the item's label, but still will trigger the menu command when pressed.
-    # They can be useful to let multiple keys be used as accelerators for the same command, e.g. WXK_ADD and WXK_NUMPAD_ADD.
+    # They can be useful to let multiple keys be used as accelerators for the same command, e.g. {Wx::K_ADD} and {Wx::K_NUMPAD}_ADD.
     # Availability:  only available for the {Wx::MSW}, {Wx::GTK} ports.  {Wx::msw},{Wx::gtk}
     # @param accel [Wx::AcceleratorEntry] 
     # @return [void]
@@ -283,6 +285,7 @@ module Wx
     # For the custom (non-stock) menu items, text must be specified and while helpString may be left empty, it's recommended to pass the item description (which is automatically shown by the library in the status bar when the menu item is selected) in this parameter.
     # Finally note that you can e.g. use a stock menu label without using its stock help string:
     # 
+    # ```
     #   // use all stock properties:
     #   helpMenu->Append(wxID_ABOUT);
     #   
@@ -293,6 +296,7 @@ module Wx
     #   wxMenuItem *mymenu = new wxMenuItem(helpMenu, wxID_ABOUT);
     #   mymenu->SetBitmap(wxArtProvider::GetBitmap(wxART_WARNING));
     #   helpMenu->Append(mymenu);
+    # ```
     # 
     # that is, stock properties are set independently one from the other.
     # @param parentMenu [Wx::Menu]  Menu that the menu item belongs to. Can be NULL if the item is going to be added to the menu later.
@@ -318,7 +322,9 @@ module Wx
     # Strips all accelerator characters and mnemonics from the given text.
     # For example:
     # 
+    # ```
     #   wxMenuItem::GetLabelText("&Hello\tCtrl-h");
+    # ```
     # 
     # will return just <code>"Hello"</code>.
     # @see Wx::MenuItem#get_item_label_text

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

@@ -14,11 +14,12 @@ module Wx
   # This is a convenient function which is usually used instead of using {Wx::MessageDialog} directly. Notice however that some of the features, such as extended text and custom labels for the message box buttons, are not provided by this function but only by {Wx::MessageDialog}.
   # The return value is one of: {Wx::YES}, {Wx::NO}, {Wx::CANCEL}, {Wx::OK} or {Wx::HELP} (notice that this return value is <b>different</b> from the return value of {Wx::MessageDialog#show_modal}).
   # For example: 
-  # 
+  # ```
   #   int answer = wxMessageBox("Quit program?", "Confirm",
   #                             wxYES_NO | wxCANCEL, main_frame);
   #   if (answer == wxYES)
   #       main_frame->Close();
+  # ```
   # 
   # message may contain newline characters, in which case the message will be split into separate lines, to cater for large messages.
   # @param message [String]  Message to show in the dialog.
@@ -121,18 +122,20 @@ module Wx
     
     # Overrides the default labels of the Yes and No buttons.
     # The arguments of this function can be either strings or one of the standard identifiers, such as {Wx::StandardID::ID_APPLY} or {Wx::StandardID::ID_OPEN}. Notice that even if the label is specified as an identifier, the return value of the dialog {Wx::MessageDialog#show_modal} method still remains one of {Wx::StandardID::ID_OK}, {Wx::StandardID::ID_CANCEL}, {Wx::StandardID::ID_YES} or {Wx::StandardID::ID_NO} values, i.e. this identifier changes only the label appearance but not the return code generated by the button. It is possible to mix stock identifiers and string labels in the same function call, for example: 
-    # 
+    # ```
     #   wxMessageDialog dlg(...);
     #   dlg.SetYesNoLabels(wxID_SAVE, _("&Don't save"));
+    # ```
     # 
     # Also notice that this function is not currently available on all platforms (although as of wxWidgets 2.9.0 it is implemented in all major ports), so it may return false to indicate that the labels couldn't be changed. If it returns true, the labels were set successfully.
     # Typically, if the function was used successfully, the main dialog message may need to be changed, e.g.: 
-    # 
+    # ```
     #   wxMessageDialog dlg(...);
     #   if ( dlg.SetYesNoLabels(_("&Quit"), _("&Don't quit")) )
     #       dlg.SetMessage(_("What do you want to do?"));
     #   else // buttons have standard "Yes"/"No" values, so rephrase the question
     #       dlg.SetMessage(_("Do you really want to quit?"));
+    # ```
     # @param yes [ButtonLabel] 
     # @param no [ButtonLabel] 
     # @return [true,false]

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

@@ -13,16 +13,10 @@ module Wx
   # 
   # Category:  Device Contexts
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class MirrorDC < DC
   
-    # Creates a (maybe) mirrored DC associated with the real dc.
-    # Everything drawn on {Wx::MirrorDC} will appear (and maybe mirrored) on dc.
-    # mirror specifies if we do mirror (if it is true) or not (if it is false).
-    # @param dc [Wx::DC] 
-    # @param mirror [true,false] 
-    # @return [MirrorDC]
-    def initialize(dc, mirror) end
-    
   end # MirrorDC
   
 

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

@@ -16,6 +16,8 @@ module Wx
   # @see  Wx::MouseEvent 
   # 
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class MouseState < KeyboardState
   
     # Returns the physical mouse position.

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

@@ -26,8 +26,6 @@ module Wx
   
     # Constructor taking an array of {Wx::String} choices.
     # Use {Wx::MultiChoiceDialog#show_modal} to show the dialog.
-    # 
-    # <b>{Wx::Perl} Note:</b> Use an array reference for the choices parameter.
     # @param parent [Wx::Window]  Parent window.
     # @param message [String]  Message to show on the dialog.
     # @param caption [String]  The dialog caption.

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

@@ -26,12 +26,13 @@ module Wx
     #   Set the window shape to the given path.
     #   Set the window shape to the interior of the given path and also draw the window border along the specified path.
     #   For example, to make a clock-like circular window you could use 
-    #   
+    #   ```
     #     wxSize size = GetSize();
     #     wxGraphicsPath
     #         path = wxGraphicsRenderer::GetDefaultRenderer()->CreatePath();
     #     path.AddCircle(size.x/2, size.y/2, 30);
     #     SetShape(path);
+    #   ```
     #   
     #   Note that windows with non default shape have a fixed size and can't be resized using {Wx::NonOwnedWindow#set_size}.
     #   As the overload above, this method is not guaranteed to work on all platforms but currently does work in {Wx::MSW}, {Wx::OSX}/Cocoa and {Wx::GTK} (with the appropriate but almost always present X11 extensions) ports.

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

@@ -85,16 +85,18 @@ module Wx
   # 
   # 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: 
-  # 
+  # ```
   #   wxSystemOptions::SetOption("msw.notebook.themed-background", 0);
+  # ```
   # 
   # Set the value to 1 to enable it again. To give a single page a solid background that more or less fits in with the overall theme, use: 
-  # 
+  # ```
   #   wxColour col = notebook->GetThemeBackgroundColour();
   #   if (col.IsOk())
   #   {
   #       page->SetBackgroundColour(col);
   #   }
+  # ```
   # 
   # On platforms other than Windows, or if the application is not using Windows themes, {Wx::Notebook#get_theme_background_colour} will return an uninitialised colour object, and the above code will therefore work on all platforms.
   # === 

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

@@ -20,14 +20,10 @@ module Wx
   # @see  Wx::ScreenDC 
   # 
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PaintDC < ClientDC
   
-    # Constructor.
-    # Pass a pointer to the window on which you wish to paint.
-    # @param window [Wx::Window] 
-    # @return [PaintDC]
-    def initialize(window) end
-    
   end # PaintDC
   
 

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

@@ -21,6 +21,8 @@ module Wx
   # @see  Wx::Bitmap 
   # 
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class Palette < GDIObject
   
     # @overload initialize()
@@ -32,7 +34,7 @@ module Wx
     #   @return [Palette]
     # @overload initialize(n, red, green, blue)
     #   Creates a palette from arrays of size n, one for each red, blue or green component.
-    #   <b>{Wx::Perl} Note:</b> In {Wx::Perl} this method takes as parameters 3 array references (they must be of the same length).
+    #   
     #   @see Wx::Palette#create 
     #   @param n [Integer]  The number of indices in the palette.
     #   @param red [unsigned char]  An array of red values.
@@ -68,8 +70,6 @@ module Wx
     
     # Returns RGB values for a given palette index.
     # true if the operation was successful.
-    # 
-    # <b>{Wx::Perl} Note:</b> In {Wx::Perl} this method takes only the pixel parameter and returns a 3-element list (or the empty list upon failure).
     # @see Wx::Palette#get_pixel 
     # @param pixel [Integer]  The palette index.
     # @param red [unsigned char]  Receives the red value.

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

@@ -193,6 +193,8 @@ module Wx
   # @see  Wx::DC#set_pen 
   # 
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class Pen < GDIObject
   
     # @overload set_colour(colour)
@@ -387,9 +389,12 @@ module Wx
   
   # This class is a helper used for {Wx::Pen} creation using named parameter idiom: it allows specifying various {Wx::Pen} attributes using the chained calls to its clearly named methods instead of passing them in the fixed order to {Wx::Pen} constructors.
   # For instance, to create a dotted blue pen with the given join style you could do 
-  # 
+  # ```
   #   wxPen pen(wxPenInfo(*wxBLUE).Style(wxPENSTYLE_DOT).Join(wxJOIN_BEVEL));
+  # ```
+  # 
   # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PenInfo < ::Object
   
     # @param colour [Wx::Colour,String,Symbol] 

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

@@ -23,8 +23,9 @@ module Wx::PG
   
   # Base class for custom {Wx::PG::PropertyGrid} editors.
   # - Names of built-in property editors are: TextCtrl, Choice, ComboBox, CheckBox, TextCtrlAndButton, and ChoiceAndButton. Additional editors include SpinCtrl and DatePickerCtrl, but using them requires calling {Wx::PG::PropertyGrid#register_additional_editors} prior use.- Pointer to built-in editor is available as {Wx::PGEditor_EditorName} (e.g. {Wx::PG_EDITOR_TEXT_CTRL}).- Before you start using new editor you just created, you need to register it using static function {Wx::PG::PropertyGrid.register_editor_class}, with code like this: 
-  # 
+  # ```
   # wxPGEditor* editorPointer = wxPropertyGrid::RegisterEditorClass(new MyEditorClass(), "MyEditor");
+  # ```
   # After that, {Wx::PG::PropertyGrid} will take ownership of the given object, but you should still store editorPointer somewhere, so you can pass it to {Wx::PG::PGProperty#set_editor}, or return it from {Wx::PG::PGEditor#do_get_editor_class}.
   # 
   # === 

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

@@ -10,6 +10,7 @@ module Wx::PG
   # You will need to create a new property editor class, override CreateControls, and have it return {Wx::PG::PGMultiButton} instance in Wx::PGWindowList#set_secondary.
   # For instance, here we add three buttons to a TextCtrl editor:
   # 
+  # ```
   #   #include <wx/propgrid/editors.h>
   #   
   #   class wxSampleMultiButtonEditor : public wxPGTextCtrlEditor
@@ -89,9 +90,11 @@ module Wx::PG
   #       }
   #       return wxPGTextCtrlEditor::OnEvent(propGrid, property, ctrl, event);
   #   }
+  # ```
   # 
   # Further to use this editor, code like this can be used:
   # 
+  # ```
   #   // Register editor class - needs only to be called once
   #   wxPGEditor* multiButtonEditor = new wxSampleMultiButtonEditor();
   #   wxPropertyGrid::RegisterEditorClass( multiButtonEditor );
@@ -101,6 +104,7 @@ module Wx::PG
   #   
   #   // Change property to use editor created in the previous code segment
   #   propGrid->SetPropertyEditor( "MultipleButtons", multiButtonEditor );
+  # ```
   # 
   # === 
   # 

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

@@ -216,6 +216,7 @@ module Wx::PG
     # Note that this function is usually called at the time that value of this property, or given child property, is still pending for change, and as such, result of {Wx::PG::FlagsProperty#get_value} or m_value should not be relied on.
     # Sample pseudo-code implementation:
     # 
+    # ```
     #   wxVariant MyProperty::ChildChanged( wxVariant& thisValue,
     #                                       int childIndex,
     #                                       wxVariant& childValue ) const
@@ -240,6 +241,7 @@ module Wx::PG
     #       // Return altered data
     #       return data;
     #   }
+    # ```
     # 
     # Modified value of the whole property.
     # @param thisValue [Wx::Variant]  Value of this property. Changed value should be returned (in previous versions of {Wx::PG::PropertyGrid} it was only necessary to write value back to this argument).
@@ -639,6 +641,7 @@ module Wx::PG
     # Setting validator explicitly via SetPropertyValidator will override this.
     # In most situations, code like this should work well (macros are used to maintain one actual validator instance, so on the second call the function exits within the first macro):
     # 
+    # ```
     #   wxValidator* wxMyPropertyClass::DoGetValidator () const
     #   {
     #       WX_PG_DOGETVALIDATOR_ENTRY()
@@ -649,6 +652,7 @@ module Wx::PG
     #   
     #       WX_PG_DOGETVALIDATOR_EXIT(validator)
     #   }
+    # ```
     # 
     # You can get common filename validator by returning {Wx::PG::FileProperty.get_class_validator}. {Wx::PG::DirProperty}, for example, uses it.
     # @return [Wx::Validator]
@@ -725,6 +729,7 @@ module Wx::PG
     # Setting validator explicitly via SetPropertyValidator will override this.
     # In most situations, code like this should work well (macros are used to maintain one actual validator instance, so on the second call the function exits within the first macro):
     # 
+    # ```
     #   wxValidator* wxMyPropertyClass::DoGetValidator () const
     #   {
     #       WX_PG_DOGETVALIDATOR_ENTRY()
@@ -735,6 +740,7 @@ module Wx::PG
     #   
     #       WX_PG_DOGETVALIDATOR_EXIT(validator)
     #   }
+    # ```
     # 
     # You can get common filename validator by returning {Wx::PG::FileProperty.get_class_validator}. {Wx::PG::DirProperty}, for example, uses it.
     # @return [Wx::Validator]
@@ -853,7 +859,7 @@ module Wx::PG
     # @param dc [Wx::DC]  {Wx::DC} to paint on.
     # @param rect [Wx::Rect]  Box reserved for custom graphics. Includes surrounding rectangle, if any. If x+width is < 0, then this is a measure item call (see above).
     # @param paintdata [Wx::PGPaintData]  {Wx::PG::PGPaintData} structure with much useful data about painted item. 
-    #   
+    #   ```
     #     struct wxPGPaintData
     #     {
     #         // wxPropertyGrid.
@@ -868,6 +874,7 @@ module Wx::PG
     #         // In a measure item call, set this to the height of item at m_choiceItem index
     #         int                     m_drawnHeight;
     #     };
+    #   ```
     # @return [void]
     def on_custom_paint(dc, rect, paintdata) end
     
@@ -910,6 +917,7 @@ module Wx::PG
     # Note that this function is usually called at the time that value of this property, or given child property, is still pending for change, and as such, result of {Wx::PG::FontProperty#get_value} or m_value should not be relied on.
     # Sample pseudo-code implementation:
     # 
+    # ```
     #   wxVariant MyProperty::ChildChanged( wxVariant& thisValue,
     #                                       int childIndex,
     #                                       wxVariant& childValue ) const
@@ -934,6 +942,7 @@ module Wx::PG
     #       // Return altered data
     #       return data;
     #   }
+    # ```
     # 
     # Modified value of the whole property.
     # @param thisValue [Wx::Variant]  Value of this property. Changed value should be returned (in previous versions of {Wx::PG::PropertyGrid} it was only necessary to write value back to this argument).
@@ -1243,24 +1252,32 @@ module Wx::PG
   # <b>Example how to use seamless 64-bit integer support</b>
   # Getting value:
   # 
+  # ```
   #   wxLongLong_t value = pg->GetPropertyValueAsLongLong();
+  # ```
   # 
   # or
   # 
+  # ```
   #   wxLongLong_t value;
   #   wxVariant variant = property->GetValue();
   #   if ( variant.GetType() == "wxLongLong" )
   #       value = wxLongLongFromVariant(variant);
   #   else
   #       value = variant.GetLong();
+  # ```
   # 
   # Setting value:
   # 
+  # ```
   #   pg->SetPropertyValue(longLongVal);
+  # ```
   # 
   # or
   # 
+  # ```
   #   property->SetValue(WXVARIANT(longLongVal));
+  # ```
   # 
   # <b>Supported special attributes:</b>
   # - {Wx::PG::PG_ATTR_MIN}, {Wx::PG::PG_ATTR_MAX}, {Wx::PG::PG_ATTR_SPINCTRL_STEP}, {Wx::PG::PG_ATTR_SPINCTRL_WRAP}, {Wx::PG::PG_ATTR_SPINCTRL_MOTION}: like in {Wx::PG::NumericProperty}.
@@ -1321,6 +1338,7 @@ module Wx::PG
     # Setting validator explicitly via SetPropertyValidator will override this.
     # In most situations, code like this should work well (macros are used to maintain one actual validator instance, so on the second call the function exits within the first macro):
     # 
+    # ```
     #   wxValidator* wxMyPropertyClass::DoGetValidator () const
     #   {
     #       WX_PG_DOGETVALIDATOR_ENTRY()
@@ -1331,6 +1349,7 @@ module Wx::PG
     #   
     #       WX_PG_DOGETVALIDATOR_EXIT(validator)
     #   }
+    # ```
     # 
     # You can get common filename validator by returning {Wx::PG::FileProperty.get_class_validator}. {Wx::PG::DirProperty}, for example, uses it.
     # @return [Wx::Validator]
@@ -1452,6 +1471,7 @@ module Wx::PG
     # Setting validator explicitly via SetPropertyValidator will override this.
     # In most situations, code like this should work well (macros are used to maintain one actual validator instance, so on the second call the function exits within the first macro):
     # 
+    # ```
     #   wxValidator* wxMyPropertyClass::DoGetValidator () const
     #   {
     #       WX_PG_DOGETVALIDATOR_ENTRY()
@@ -1462,6 +1482,7 @@ module Wx::PG
     #   
     #       WX_PG_DOGETVALIDATOR_EXIT(validator)
     #   }
+    # ```
     # 
     # You can get common filename validator by returning {Wx::PG::FileProperty.get_class_validator}. {Wx::PG::DirProperty}, for example, uses it.
     # @return [Wx::Validator]
@@ -1604,6 +1625,7 @@ module Wx::PG
     # Setting validator explicitly via SetPropertyValidator will override this.
     # In most situations, code like this should work well (macros are used to maintain one actual validator instance, so on the second call the function exits within the first macro):
     # 
+    # ```
     #   wxValidator* wxMyPropertyClass::DoGetValidator () const
     #   {
     #       WX_PG_DOGETVALIDATOR_ENTRY()
@@ -1614,6 +1636,7 @@ module Wx::PG
     #   
     #       WX_PG_DOGETVALIDATOR_EXIT(validator)
     #   }
+    # ```
     # 
     # You can get common filename validator by returning {Wx::PG::FileProperty.get_class_validator}. {Wx::PG::DirProperty}, for example, uses it.
     # @return [Wx::Validator]
@@ -1865,7 +1888,7 @@ module Wx::PG
     # @param dc [Wx::DC]  {Wx::DC} to paint on.
     # @param rect [Wx::Rect]  Box reserved for custom graphics. Includes surrounding rectangle, if any. If x+width is < 0, then this is a measure item call (see above).
     # @param paintdata [Wx::PGPaintData]  {Wx::PG::PGPaintData} structure with much useful data about painted item. 
-    #   
+    #   ```
     #     struct wxPGPaintData
     #     {
     #         // wxPropertyGrid.
@@ -1880,6 +1903,7 @@ module Wx::PG
     #         // In a measure item call, set this to the height of item at m_choiceItem index
     #         int                     m_drawnHeight;
     #     };
+    #   ```
     # @return [void]
     def on_custom_paint(dc, rect, paintdata) end
     
@@ -2023,7 +2047,7 @@ module Wx::PG
     # @param dc [Wx::DC]  {Wx::DC} to paint on.
     # @param rect [Wx::Rect]  Box reserved for custom graphics. Includes surrounding rectangle, if any. If x+width is < 0, then this is a measure item call (see above).
     # @param paintdata [Wx::PGPaintData]  {Wx::PG::PGPaintData} structure with much useful data about painted item. 
-    #   
+    #   ```
     #     struct wxPGPaintData
     #     {
     #         // wxPropertyGrid.
@@ -2038,6 +2062,7 @@ module Wx::PG
     #         // In a measure item call, set this to the height of item at m_choiceItem index
     #         int                     m_drawnHeight;
     #     };
+    #   ```
     # @return [void]
     def on_custom_paint(dc, rect, paintdata) end
     
@@ -2129,6 +2154,8 @@ module Wx::PG
   # Because text, background and other colours tend to differ between platforms, {Wx::PG::SystemColourProperty} must be able to select between system colour and, when necessary, to pick a custom one.
   # {Wx::PG::SystemColourProperty} value makes this possible.
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class ColourPropertyValue < Object
   
     # An integer value relating to the colour, and which exact meaning depends on the property with which it is used.