Remove misleading Doxygen comments copied from the comments in C++
header which didn't make sense here.
Improve the documentation of menu ID ranges.
(cherry picked from commit 5a95c14a39)
It was added back in 345319d60c (fixes to menu stock items support
(patch 1547639), 2006-09-05) and even if it's not particularly useful,
it still should be documented, so add documentation for it.
See #8090.
(cherry picked from commit e80d78c2c9)
Mention wxDIALOG_NO_PARENT in the documentation of the parent parameter
as people who don't know about this style are not going to see this
style documentation either.
See #23560.
(cherry picked from commit 8245e1073a)
The changes of 1f7a8a8 (Round, rather than truncate, in wxSize and
wxPoint operations, 2018-03-06) have invalidated the documentation that
had been previously added in 4c20f3d (Document that wxPoint(wxRealPoint)
ctor truncates, not rounds., 2013-04-16) to document the old behaviour.
Changing the behaviour once again doesn't seem to be desirable, but at
least synchronize the documentation with it again.
See #26099.
(cherry picked from commit eb64d55ea9)
Call it "inc" instead of "value" because this is what it actually is and
for consistency with the actual header and SetIncrement() in
wxSpinCtrlDouble.
See #26002.
(cherry picked from commit 666966acbf)
This ctor was wrongly documented back in cfa9866bf5 (revision
contributed by Utensil Candel, 2008-03-30) to call IncRef() on the
pointer passed to it but in fact it just takes ownership of it.
See #25692.
(cherry picked from commit ea0a01879f)
Protect gs_platInfo initialization with a critical section to ensure
that we don't try to do it in parallel from more than one thread,
resulting in crashes.
See #25459, #25464.
(cherry picked from commit a26eda72e8)
When the sizer is completely empty, it makes more sense to return 0
from these functions without asserting.
See #25642, #25641.
(cherry picked from commit d1be72aa8e)
This function exists since always, but somehow was never documented.
Do it now, better late than never.
(cherry picked from commit 8a6efbf5bb91e8fec7f77c4f5096daa663f74520)
Don't an unnecessary documentation group, this results in these ctors
being documented in a separate documentation section from all the other
ctors.
See #25113.
(cherry picked from commit d1aa050721)
This function should be atomic, unlike our own code doing copy+remove if
rename fails (as it always will under MSW if the destination exists).
(cherry picked from commit 02e6ad2560)
Recognize Windows Server 2025 in wxGetOsDescription()
and update Windows OS table in wxGetOsVersion() docs.
See #25066.
(cherry picked from commit c88c86ece9)
Fix the flag name in wxSizerFlags::Shaped() description.
Add a reference to Windows Sizing Overview to Window Layout page and
Sizers Overview.
Add a reference to Sizers Overview to Window Sizing Overview.
Closes#25044.
(cherry picked from commit e0b055e53b)
Unfortunately returning false from the (overridden) wxApp::OnInit() has
a side effect of exiting the application with inconsistent error code:
255 under Unix but 127 under MSW with MSVC.
While changing the default exit code in this case is probably a bad idea
because there are surely people relying on the current values, at least
allow changing it by explicitly calling the new SetErrorExitCode()
function.
Unlike the version in master, this commit uses a global variable for the
exit code value to avoid changing the ABI.
(cherry picked from commit e2de7dc625)
Use "WX" prefix for it, just as for all the other constants in the same
enum instead of the lower-case "wx" (which is still preserved for
compatibility).
See #24964, #24965.
(cherry picked from commit 7af7c55ed0)
Define wxWARN_UNUSED always as nothing, unless wxNO_UNUSED_VARIABLES is
defined by the library user.
Also opt-in for wxWARN_UNUSED when building wxWidgets itself, i.e. when
WXBUILDING is defined.
Also known as [[gnu::warn_unused]].
Use __has_attribute to check availability of the attribute. (Is available
on recent GCC and Clang versions, not available on MSVC.)
(cherry picked from commit a2e2bc57c9)
It seems that as of the below commit, doxygen changed its handling of
parsing backticks in comments such that it now fails to properly
generate documentation for the entire datetime.h file. Fix this by
closing the open backtick.
Also update the actual, non-documentation, header to match for
consistency, even if non-matching backticks are not a problem there.
See: https://github.com/doxygen/doxygen/commit/f18767307be20ca8d2ca81f74cc1f3446205282b
See #24814.
(cherry picked from commit 2d79dfc7a2)
Map this value to an empty string instead of crashing.
See #24741.
Co-authored-by: Vadim Zeitlin <vadim@wxwidgets.org>
(cherry picked from commit 1b6bfff1d8)
Add a convenient helper allowing to select between the two colours
depending on whether we're using light or dark mode.
Use this in a couple of places instead of manual tests for IsDark().
No real changes.
(cherry picked from commit 30dc3350dc)
Knowing msgIdLanguage is necessary for correct evaluation of preferred
languages order; without it, it would be possible to load undesirable
translation file.
See 2af36e9560 for details.
Update Windows Server information.
Additionally, add a note to wxGetOsDescription() source to
keep the table in docs in the sync with the code.
See #24653.
(cherry picked from commit 73e28e2b65)
This isn't the case any more since a long time, see 89a7e1ff98 (Added
wxLOCALE_DATE/TIME_FMT support to wxLocale::GetInfo()., 2009-03-29).
(cherry picked from commit 0cc5c37429)
Document all available styles, i.e., just like with wxSpinCtrl, list
also wxTE_PROCESS_ENTER and the three text alignment options.
See #24488.
(cherry picked from commit 86e4660ba6)
Although TAB and Ctrl+I generate the same key code in the events passed
to wxEVT_CHAR handlers, it seems more reasonable to only consider the
former to be in "TAB category", but not the latter.
See #10268, #24254, #24258.
(cherry picked from commit 460c35ff0e)
Only show the native dialogs using system dpi-awereness, when there are
displays with different DPI.
And add the msw.native-dialogs-pmdpi option to also show the dialogs
using per-monitor dpi-awareness when there are displays with different
DPI.
This is a combined cherry-pick of 5ae3b771ad (Merge branch
'win32-native-dialogs-pmdpi' of https://github.com/MaartenBent/wxWidgets,
2024-01-19) and c72f4efc9c (Fix crash when closing a wxColourDialog
under MSW, 2024-02-06)
See #24121, #24196, #24288.
This used to be possible in 3.0 but was disallowed back in 29bf859fae
(Check if new index is in range before selecting new value in
wxPGProperty::SetChoiceSelection., 2014-11-29). However there doesn't
seem to be any real harm in still allowing to do this, so handle -1 as a
special case here.
See #24279, #24281.
(cherry picked from commit a6cc89777b)
Ensure they're present in the interface header as this is also required
for wrapping them in other languages, such as Python.
See #24209.
(cherry picked from commit 81e9373efa)
Use the correct types instead of wxSize which was erroneously used
there ever since a5664fd6ef (Increase interoperability between wxPoint
and wxRealPoint introducing constructors which convert between the two
classes., 2010-06-09).
See #23804, #24186.
(cherry picked from commit a8b14edc40)
Use the same argument name as in the actual code in the class
constructor as well as the convenience function, instead of
wrongly copypasted "book".
See also 33de6dc (Fix confusing wxPersistentTLW ctor argument name,
2023-12-22).
See #24158.
(cherry picked from commit 24952d0203)