Replace -1 with wxCOL_WIDTH_DEFAULT in the header and the documentation
for clarity.
See #23307, #23325.
(cherry picked from commit cf3dcb230a009c6748dc9eb986df805edfac84b4)
Explain the special meaning of 0 and negative values in this function.
See #23299.
(cherry picked from commit 809d2918ccd01ac029ff3d0bc3a143c140832862)
There is no real need to document this, it's not a valid enum value and
having it in this file without a trailing comma was a syntax error.
Closes#23298.
(cherry picked from commit 5b6b644e8bcb5b9503ff1a5fb49b2db768cb625c)
This function replaces the existing GetSystemLocale() as it can
represent the locales that don't have any corresponding wxLanguage
values and for which GetSystemLocale() has no choice but to return
wxLANGUAGE_UNKNOWN.
(cherry picked from commit 14714856b3956d52ede8bcf27345fdc6efd438e9)
The wxUILocale function really returns the default language unlike the
one in wxLocale which must kepe using the default locale for
compatibility, making its name confusing.
(cherry picked from commit ce04dbc0247aa548680f753568f9c9c39a4236b9)
Fix another pixel units confusion in wxToolBar code and ensure that
"sizeNeeded" is expressed in logical units when a fixed bitmap size is
set, to make it consistent with the case when it is not set, and also
because bitmap size is supposed to be expressed in logical pixels, in
both SetToolBitmapSize() and, for consistency, GetToolBitmapSize() too.
Also explicitly mention the latter in the documentation.
See #23228, #23222.
(cherry picked from commit 453a52b942fa27c8f412716c8290dbcb6172d0e4)
The documentation for wxChoiceBook discusses using this method, but it
was not previously documented.
See #23211.
Co-Authored-By: Vadim Zeitlin <vadim@wxwidgets.org>
(cherry picked from commit 3cc00091e2d251f9b6cae20dc997f068604e0b4f)
This is another instance of the problem mostly fixed back in a193a6786d
(Escape space after "e.g." or "i.e." in the manual., 2014-12-24),
See #22925.
(cherry picked from commit fd8453ed08a03416c789df6f7e0bed9509e31309)
Make it clear that wxEVT_TREE_END_LABEL_EDIT is sent whether the user
accepts or cancels editing the label.
See #22867.
(cherry picked from commit 6e940d1a108bbf4a07586d32f0d8061beb63f927)
It doesn't derive from wxTextCtrl in all ports, even if it does in some
of them.
See #22951.
(cherry picked from commit 76145b377ccdc59d4e0f9d5a402efcb863dfebe3)
It had an extra underscore in it (EVT_WEBVIEW_FULL_SCREEN_CHANGED).
See #22947, #22948.
(cherry picked from commit fc9c9c0e1bbdbc0038bda070fc640b413f00b454)
Use a custom NSTableHeaderView subclass just to be able to override
rightMouseDown: in it and generate this event, as there is no direct
support for this at NSOutlineView level.
See #22833.
(cherry picked from commit 5ac9b4897192a3545cc1cd1b814a130ddc191cab)
Add a note that data has to be null terminated with the variants
without len parameter and to use the third variant for data
that is not null terminated.
See #22838.
(cherry picked from commit 17934d3d624a93b39b9c4935e2086d6ab0d54c1a)
Don't use @code as we don't want the expression to appear on its own
line(s).
Also use Markdown `` instead of Doxygen @c as the former is more general
and can be used around arbitrary runs of text.
(cherry picked from commit 3bf8a60c6c1be7de663ab114100898fa9e0abe36)
Add an SVG and a wxBitmapBundleImpl to the list of methods that can be
used when creating a wxBitmapBundle.
Remove a generic sentence promising adding other methods of creating
bundles in the future.
See #22774.
(cherry picked from commit 17371d911d9ec68b0c2d98c7f56977523803b392)
Make GTK notebook log suppression opt-in to avoid a fatal error when the
application calls g_log_set_writer_func() itself, as doing it more than
once immediately kills the application with glib 2.73 and there is no
way to check if it had been already done or not (you have to admire the
purity of the API design here).
This is unfortunate as 99% of the wxWidgets applications that do _not_
call g_log_set_writer_func() would now show the spurious diagnostics by
default again, but preferable to making the remaining 1% crash, and
there doesn't seem to be any other solution.
Call the new GTKAllowDiagnosticsControl() function in the notebook
sample to at least still avoid getting the spurious diagnostic messages
described in #22176 there.
See #22717.
(cherry picked from commit 8af645ed229ebb2542769775565ce85c158e4fb1 and
adapted to 3.2 stable ABI).
In many cases it should be 'either', and 'nor' should be 'or'
accordingly.
No changes to actual code.
See #22723.
(cherry picked from commit 66916c74a3d44e8bc1b30cf42309e36e5d9e9135)
This function is useful and there is no reason to exclude it from public
API and it should have been done back in 00224e3f30 (Add
wxGrid::RefreshBlock() helper, 2019-07-11) when it was added.
(cherry picked from commit 7999102295c81ccda5a0a07f55fec47e8e0fa8d9)
Fix wrong use of Doxygen grouping-related markup which somehow worked in
older Doxygen versions, but doesn't work any longer.
This fixes the problem with the "Functions by Category" pages being
empty in the resulting HTML documentation and wrong documentation being
shown for a bunch of wxString members.
This is a combined cherry-pick of the following master commits:
bd92523bc5 Fix use of Doxygen @addtogroup command
4c46e01b14 Remove stray Doxygen end group marker
8ac10d28f8 Fix all the other comments with Doxygen grouping commands too
c0f1ecf263 Fix another unbalanced Doxygen grouping command after last commit
See #22248, #22572.
New version of Doxygen interprets __foo__ as Markdown markup and
consumes the underscores, which mangles the identifier.
Prevent this from happening by escaping the leading underscore for all
occurrences of "__" outside of the code blocks, this seems to be the
least intrusive fix.
See #22671.
(cherry picked from commit 57bf9c5af5258f1f0f20d75c708dcec9d876b6e2)
Notably explain that the first parameter should contain the number of
rows/columns when appending, not the position.
(cherry picked from commit c15c0040dbb80d20251674f7e582d75d0b1962c2)
Don't imply that the function returns false for the empty capture groups
because this is not the case (and never was).
See #22708.
(cherry picked from commit 537f11fd4d258d11454a75fa5891e4f011ff0da5)
This is a backport of #22635 with the following changes:
- Don't make the new function virtual to avoid changing ABI.
- Use wxABI_VERSION checks around the declarations of the new
functions (and also constants, for good measure).
- Add new symbol to the linker version script (creating a new
section for it).
- Document the function as being new in 3.2.1, not 3.3.0.
See #22543.
Unlike SetSize(), passing -1 to this function doesn't preserve the
existing size in the corresponding direction.
(cherry picked from commit 134862a4648f594d3de766b00c55ff730e12d03b)
Replace "’s" with "'s" in interface headers as the former broke wxPython
build with SIP under MSW.
See #22605.
(cherry picked from commit 4010140491a4db4067a7754e6cf2ea7dd71e2161)
Some versions consist of four parts with the last part being called the
revision or build number. wxVersionInfo is now able to save such a
fourth number.
Add another compatibility implicit constructor to allow the existing
code, directly passing XPM data to various functions that used to take
wxBitmap or wxIcon and now taking wxBitmapBundle, to work.
Closes#22566.
Don't change the window size automatically if the application handled
wxEVT_DPI_CHANGED event to allow it to choose a better size than what is
suggested by MSW itself.
Closes#19152.
Make wxINVERT logical function work in at least some circumstances with
wxGTK3/X11 and use this to make wxSplitterWindow and wxSashWindow
separator visible during resizing.
See #22546.
Closes#16890.
HasAlpha() was already available in most of them, now ensure that it's
present in all of them, especially as it has a reasonable default
implementation.
UseAlpha() was only present in wxMSW and wxOSX and still remains only
implemented there, but provide at least a stub for it elsewhere as well
to avoid problems such as that of #17393.
See #22545.
Closes#17397.
Neither of these methods was actually ever used after the changes of the
last two commits (and they hadn't been used when not using wxGTK even
before), so don't force the user-defined model classes to override them.
Also stop using them, as the stub versions don't return correct values
any longer.
Still keep the virtual functions in the base class for compatibility
however as it doesn't cost us much and avoids breaking the existing code
using "override".
This is implemented in Cairo and CoreGraphics renderers only, but this
is still useful as these renderers are used on the platforms where wxDC
wxINVERT logical function is not supported and this composition mode can
partially replace it.
