wxruby3 0.9.0.pre.beta.14-x64-mingw-ucrt → 0.9.0.pre.rc.2-x64-mingw-ucrt

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.

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

@@ -354,14 +354,16 @@ module Wx::PG
   # 
   # 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:
   # 
+  # ```
   #   wxLongLong ll;
   #   ll << property->GetValue();
   #   
   #   // or
   #   wxLongLong ll = propertyGrid->GetPropertyValueAsLong(property);
+  # ```
   # 
   # Getting 64-bit value: 
-  # 
+  # ```
   #   wxLongLong_t value = pg->GetPropertyValueAsLongLong();
   #   
   #   // or
@@ -372,14 +374,16 @@ module Wx::PG
   #       value = variant.GetLongLong();
   #   else
   #       value = variant.GetLong();
+  # ```
   # 
   # Setting 64-bit value: 
-  # 
+  # ```
   #   pg->SetPropertyValue(longLongVal);
   #   
   #   // or
   #   
   #   property->SetValue(WXVARIANT(longLongVal));
+  # ```
   # 
   # Supported special attributes:
   # - {Wx::PG::PG_ATTR_MIN}, {Wx::PG::PG_ATTR_MAX} to specify acceptable value range.- {Wx::PG::PG_ATTR_SPINCTRL_STEP}, {Wx::PG::PG_ATTR_SPINCTRL_WRAP}, {Wx::PG::PG_ATTR_SPINCTRL_MOTION}: Sets SpinCtrl editor parameters. 
@@ -558,6 +562,7 @@ module Wx::PG
   # 
   # 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).
   # 
+  # ```
   #   class wxColourPropertyValue : public wxObject
   #   {
   #   public:
@@ -572,9 +577,11 @@ module Wx::PG
   #       // Resulting colour. Should be correct regardless of type.
   #       wxColour    m_colour;
   #   };
+  # ```
   # 
   # 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}.
   # 
+  # ```
   #   // Override in derived class to customize how colours are translated
   #   // to strings.
   #   virtual wxString ColourToString( const wxColour& col, int index ) const;
@@ -589,6 +596,7 @@ module Wx::PG
   #   // Returns colour for given choice.
   #   // Default function returns wxSystemSettings::GetColour(index).
   #   virtual wxColour GetColour( int index ) const;
+  # ```
   # 
   # == wxCursorProperty
   # 
@@ -599,6 +607,7 @@ module Wx::PG
   # 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:
   # 
+  # ```
   #   class MyProperty : public wxPGProperty
   #   {
   #   public:
@@ -641,10 +650,12 @@ module Wx::PG
   #   
   #   protected:
   #   };
+  # ```
   # 
   # Since {Wx::PG::PGProperty} derives from {Wx::Object}, you can use standard {Wx::DECLARE_DYNAMIC_CLASS} and {Wx::IMPLEMENT_DYNAMIC_CLASS} macros. From the above example they were omitted for sake of simplicity, and besides, they are only really needed if you need to use {Wx::RTTI} with your property class.
   # You can change the 'value type' of a property by simply assigning different type of variant with SetValue. <b>It is mandatory to implement {Wx::VariantData} class for all data types used as property values.</b> You can use macros declared in {Wx::PG::PropertyGrid} headers. For instance:
   # 
+  # ```
   #   // In header file:
   #   // (If you need to have export declaration, use version of macros
   #   // with _EXPORTED postfix)
@@ -655,6 +666,7 @@ module Wx::PG
   #   
   #   // Or, if you don't have valid == operator:
   #   WX_PG_IMPLEMENT_VARIANT_DATA_DUMMY_EQ(MyDataClass)
+  # ```
   # 
   # === 
   # 
@@ -772,6 +784,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::PGProperty#get_value} or m_value should not be relied on.
     # Sample pseudo-code implementation:
     # 
+    # ```
     #   wxVariant MyProperty::ChildChanged( wxVariant& thisValue,
     #                                       int childIndex,
     #                                       wxVariant& childValue ) const
@@ -796,6 +809,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).
@@ -812,6 +826,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()
@@ -822,6 +837,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]
@@ -836,7 +852,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.
@@ -851,6 +867,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
     
@@ -936,8 +953,9 @@ module Wx::PG
     # Sets or clears given property flag.
     # Mainly for internal use.
     # Setting a property flag never has any side-effect, and is intended almost exclusively for internal use. So, for example, if you want to disable a property, call 
-    # 
+    # ```
     #   Enable(false) 
+    # ```
     #  instead of setting {Wx::PG::PGPropertyFlags::PG_PROP_DISABLED} flag.
     # @see Wx::PG::PGProperty#has_flag
     # @see  GetFlags() 
@@ -1409,7 +1427,9 @@ module Wx::PG
     # Set default value of a property.
     # Synonymous to
     # 
+    # ```
     #   SetAttribute("DefaultValue", value);
+    # ```
     # @param value [Wx::Variant] 
     # @return [void]
     def set_default_value(value) end
@@ -1594,6 +1614,7 @@ module Wx::PG
     #   Constructor.
     #   It is protected because {Wx::PG::PGProperty} is only a base class for other property classes. Non-abstract property classes should have constructor of this style:
     #   
+    #   ```
     #     MyProperty( const wxString& label, const wxString& name, const T& value )
     #         : wxPGProperty(label, name)
     #     {
@@ -1609,6 +1630,7 @@ module Wx::PG
     #         //                                           wxPG_LABEL,
     #         //                                           value.GetSubProp1()));
     #     }
+    #   ```
     #   @param label [String] 
     #   @param name [String] 
     #   @return [PGProperty]
@@ -1625,6 +1647,8 @@ module Wx::PG
   # 
   # Category:  {Wx::PG::PropertyGrid}
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PGChoices < ::Object
   
     # @overload initialize()
@@ -1796,6 +1820,8 @@ module Wx::PG
   # Contains information related to property's OnCustomPaint.
   # 
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PGPaintData < ::Object
   
     # {Wx::PG::PropertyGrid}

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

@@ -291,6 +291,8 @@ module Wx::PG
   # Used to convey validation information to and from functions that actually perform validation.
   # Mostly used in custom property classes.
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PGValidationInfo < ::Object
   
     # 

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

@@ -125,9 +125,11 @@ module Wx::PG
     # Adds given key combination to trigger given action.
     # Here is a sample code to make Enter key press move focus to the next property.
     # 
+    # ```
     #   propGrid->AddActionTrigger(wxPG_ACTION_NEXT_PROPERTY,
     #                              WXK_RETURN);
     #   propGrid->DedicateKey(WXK_RETURN);
+    # ```
     # @param action [Integer]  Which action to trigger. See wxPropertyGrid Action Identifiers.
     # @param keycode [Integer]  Which keycode triggers the action.
     # @param modifiers [Integer]  Which key event modifiers, in addition to keycode, are needed to trigger the action.
@@ -411,8 +413,9 @@ module Wx::PG
     
     # Makes given column editable by user.
     # Note that column must not be equal to 1, as the second column is always editable and can be made read-only only on cell-by-cell basis using 
-    # 
-    #   wxPGProperty::ChangeFlag(wxPG_PROP_READONLY, true)
+    # ```
+    #   wxPGProperty::ChangeFlag(wxPG_PROP_READONLY, true) 
+    # ```
     # @see Wx::PG::PropertyGrid#begin_label_edit
     # @see  Wx::PG::PropertyGrid#end_label_edit 
     # @param column [Integer]  The index of the column to make editable.

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

@@ -419,6 +419,7 @@ module Wx::PG
     #   
     #   Example of use:
     #   
+    #   ```
     #     // append category
     #     wxPGProperty* my_cat_id = propertygrid->Append( new wxPropertyCategory("My Category") );
     #     
@@ -429,6 +430,7 @@ module Wx::PG
     #     
     #     // insert before to first item - using first variant
     #     wxPGProperty* my_item_id_2 = propertygrid->Insert( my_item_id, new wxStringProperty("My String 2") );
+    #   ```
     #   @param priorThis [String,Wx::PG::PGProperty]  New property is inserted just prior to this. Available only in the first variant. There are two versions of this function to allow this parameter to be either an id or name to a property.
     #   @param newProperty [Wx::PGProperty]  Pointer to the inserted property. {Wx::PG::PropertyGrid} will take ownership of this object.
     #   @return [Wx::PG::PGProperty]
@@ -502,8 +504,10 @@ module Wx::PG
     # Replaces property with id with newly created one.
     # For example, this code replaces existing property named "Flags" with one that will have different set of items:
     # 
+    # ```
     #   pg->ReplaceProperty("Flags",
     #       wxFlagsProperty("Flags", wxPG_LABEL, newItems))
+    # ```
     # @see Wx::PG::PropertyGridInterface#insert 
     # @param id [String,Wx::PG::PGProperty] 
     # @param property [Wx::PGProperty] 
@@ -519,12 +523,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 [true,false]
-    def restore_editable_state(src, restoreStates=Wx::PG::PropertyGridInterface::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::PropertyGridInterface::EditableStateFlags::AllStates) end
+    def save_editable_state(includedStates=Wx::PG::PropertyGridPage::EditableStateFlags::AllStates) end
     
     # Set proportion of an auto-stretchable column.
     # {Wx::PG::PG_WINDOW_STYLES::PG_SPLITTER_AUTO_CENTER} window style needs to be used to indicate that columns are auto- resizable.

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

@@ -14,6 +14,7 @@ module Wx::PG
   # {Wx::PG::PropertyGridManager} constructor has exact same format as {Wx::PG::PropertyGrid} constructor, and basically accepts same extra window style flags (albeit also has some extra ones).
   # Here's some example code for creating and populating a {Wx::PG::PropertyGridManager}:
   # 
+  # ```
   #   wxPropertyGridManager* pgMan = new wxPropertyGridManager(this, PGID,
   #       wxDefaultPosition, wxDefaultSize,
   #       // These and other similar styles are automatically
@@ -47,6 +48,7 @@ module Wx::PG
   #   
   #   // Display a header above the grid
   #   pgMan->ShowHeader();
+  # ```
   # 
   # == Window Styles
   # 

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

@@ -122,6 +122,8 @@ module Wx::PG
   # 
   # A return value from {Wx::PG::PropertyGrid#hit_test}, contains all you need to know about an arbitrary location on the grid.
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PropertyGridHitTestResult < ::Object
   
     # @return [PropertyGridHitTestResult]

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

@@ -51,7 +51,7 @@ module Wx
     
     # Returns the native implementation of the real picker control.
     # The returned control in the generic implementation of {Wx::FilePickerCtrl}, {Wx::DirPickerCtrl}, {Wx::FontPickerCtrl} and {Wx::ColourPickerCtrl} is a specialized {Wx::Button} class so that you can change its label doing, e.g.: 
-    # 
+    # ```
     #   #ifdef __WXMSW__
     #       // wxMSW is one of the platforms where the generic implementation
     #       // of wxFilePickerCtrl is used...
@@ -60,6 +60,7 @@ module Wx
     #       if (pButt)
     #           pButt->SetLabel("Custom browse string");
     #   #endif
+    # ```
     # @return [Wx::Control]
     def get_picker_ctrl; end
     alias_method :picker_ctrl, :get_picker_ctrl

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

@@ -183,9 +183,10 @@ module Wx
   # This class holds information about the operating system, the toolkit and the basic architecture bitness of the machine where the application is currently running.
   # This class does not only have getters for the information above, it also has setters. This allows you to e.g. save the current platform information in a data file (maybe in string form) so that when you later load it, you can easily retrieve (see the static getters for string->enum conversion functions) and store inside a {Wx::PlatformInfo} instance (using its setters) the signature of the system which generated it.
   # In general however you only need to use the static {Wx::PlatformInfo.get} function and then access the various information for the current platform: 
-  # 
+  # ```
   #   wxLogMessage("This application is running under %s.",
   #                wxPlatformInfo::Get().GetOperatingSystemIdName());
+  # ```
   # 
   # === 
   # 
@@ -198,6 +199,8 @@ module Wx
   # @see  User and OS 
   # 
   # 
+  # 
+  # @note This class is <b>untracked</b> and should not be derived from nor instances extended!
   class PlatformInfo < ::Object
   
     # Returns the architecture bitness ID of this {Wx::PlatformInfo} instance.

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

@@ -51,6 +51,7 @@ module Wx
   # To use this class, call {Wx::PropertySheetDialog#create} from your own Create function. Then call {Wx::PropertySheetDialog#create_buttons}, and create pages, adding them to the book control. Finally call {Wx::PropertySheetDialog#layout_dialog}.
   # For example:
   # 
+  # ```
   #   bool MyPropertySheetDialog::Create(...)
   #   {
   #       if (!wxPropertySheetDialog::Create(...))
@@ -65,6 +66,7 @@ module Wx
   #       LayoutDialog();
   #       return true;
   #   }
+  # ```
   # 
   # If necessary, override {Wx::PropertySheetDialog#create_book_ctrl} and {Wx::PropertySheetDialog#add_book_ctrl} to create and add a different kind of book control. You will then need to use two-step construction for the dialog or change the style of the book control by calling {Wx::PropertySheetDialog#set_sheet_style} before calling {Wx::PropertySheetDialog#create}.
   # The Dialogs Sample shows this class being used with notebook and toolbook controllers (for Windows-style and Mac-style settings dialogs).