diff --git a/wxPython/src/_pseudodc.i b/wxPython/src/_pseudodc.i index e2f6710c53..bd40ea6768 100644 --- a/wxPython/src/_pseudodc.i +++ b/wxPython/src/_pseudodc.i @@ -342,8 +342,10 @@ current text background colour to draw the background (all bits set to font, and the current text foreground and background colours. The coordinates refer to the top-left corner of the rectangle bounding -the string. See `GetTextExtent` for how to get the dimensions of a -text string, which can be used to position the text more precisely. +the string. See `wx.DC.GetTextExtent` for how to get the dimensions of +a text string, which can be used to position the text more precisely, +(you will need to use a real DC with GetTextExtent as wx.PseudoDC does +not implement it.) **NOTE**: under wxGTK the current logical function is used by this function but it is ignored by wxMSW. Thus, you should avoid using @@ -545,9 +547,8 @@ context, and the original palette restored.", " DocDeclStr( virtual void , SetLogicalFunction(int function), "Sets the current logical function for the device context. This -determines how a source pixel (from a pen or brush colour, or source -device context if using `Blit`) combines with a destination pixel in -the current device context. +determines how a source pixel (from a pen or brush colour, combines +with a destination pixel in the current device context. The possible values and their meaning in terms of source and destination pixel values are as follows: diff --git a/wxPython/src/_renderer.i b/wxPython/src/_renderer.i index f95f1ea916..3ee0740e0f 100644 --- a/wxPython/src/_renderer.i +++ b/wxPython/src/_renderer.i @@ -243,16 +243,16 @@ The flags parameter may be: "Return the generic implementation of the renderer. Under some platforms, this is the default renderer implementation, others have platform-specific default renderer which can be retrieved by calling -`GetDefault`.", ""); +`wx.RendererNative.GetDefault`.", ""); MustHaveApp(GetDefault); DocDeclStr( static wxRendererNative& , GetDefault(), "Return the default (native) implementation for this platform -- this -is also the one used by default but this may be changed by calling `Set` -in which case the return value of this method may be different from -the return value of `Get`.", ""); +is also the one used by default but this may be changed by calling +`wx.RendererNative.Set` in which case the return value of this method +may be different from the return value of `wx.RendererNative.Get`.", ""); diff --git a/wxPython/src/_sizers.i b/wxPython/src/_sizers.i index 1157c6a303..9726d7b4fc 100644 --- a/wxPython/src/_sizers.i +++ b/wxPython/src/_sizers.i @@ -360,8 +360,8 @@ DocStr(wxSizer, "wx.Sizer is the abstract base class used for laying out subwindows in a window. You cannot use wx.Sizer directly; instead, you will have to use one of the sizer classes derived from it such as `wx.BoxSizer`, -`wx.StaticBoxSizer`, `wx.NotebookSizer`, `wx.GridSizer`, `wx.FlexGridSizer` -and `wx.GridBagSizer`. +`wx.StaticBoxSizer`, `wx.GridSizer`, `wx.FlexGridSizer` and +`wx.GridBagSizer`. The concept implemented by sizers in wxWidgets is closely related to layout tools in other GUI toolkits, such as Java's AWT, the GTK diff --git a/wxPython/src/richtext.i b/wxPython/src/richtext.i index c99edf1ec0..12c1d69644 100644 --- a/wxPython/src/richtext.i +++ b/wxPython/src/richtext.i @@ -571,7 +571,7 @@ during sizing.", ""); virtual bool , SaveFile(const wxString& file = wxPyEmptyString, int type = wxRICHTEXT_TYPE_ANY), "Save the contents of the document to the given filename, or if the -empty string is passed then to the filename set with `SetFileName`.", ""); +empty string is passed then to the filename set with `SetFilename`.", ""); // sets/clears the dirty flag