Including the recently added docs/changes_32.txt one.
This should have been in 304f173924 (Rename the existing changelog to
changes_32.txt and add a new one, 2022-07-11) but was forgotten there.
The contents of <windowlabel> can be any window, including a panel with
its own sizer, but such panels were not created correctly due to using
the wrong value of wxSizerXmlHandler::m_parentSizer, which prevented the
sizer from being associated with the panel.
Fix this by using the same hack as elsewhere and temporarily resetting
the value of this variable before calling CreateResFromNode(). Also do
the same for m_isInside, even though it doesn't seem necessary here,
because it should always be false anyhow when <windowlabel> is parsed,
just for consistency. But don't bother doing it for m_isGBS, as it's
definitely false when handling wxStaticBoxSizer node.
The character "@", which can be part of the full language name, e.g. in
the case of "sr@latin", can't be reliably used as part of resource name,
so replace it with "_" in wxResourceTranslationsLoader.
Closes#22589.
Closes#22601.
To prevent the changelog file from growing too big, start a new one for
the next release.
Also restore the instructions about updating it from Git notes just
before the release.
Run install_name_tool on wxrc binary again: this used to be done and is
still needed, but was broken in 30915c6163 (Make wxrc independent from
GUI support, 2021-07-07) which moved the code appending the line calling
install_name_tool for wxrc to change-install-name script before this
script creation, meaning that it was simply overwritten later.
See #22620.
The space taken by the frozen part needs to be subtracted from the
available size, not added to it, as was mistakenly done before.
This fixes the problem with scrollbars not appearing correctly in the
grid even when they were clearly needed because its contents didn't fit
into the window.
See #22602.
Don't use operator<<() with a wide char string, as this overload has
been removed in C++20. This can be done simply by not using wide char
string at all in this test, as it's not really needed.
Co-Authored-By: Vadim Zeitlin <vadim@wxwidgets.org>
Closes#22599.
Extracting the lower part of a 64-bit value only works when long is
32-bit, but not if it's 64-bit as well as is the case under LP64 Unix
systems.
Just use a normal cast to long instead, as this is simpler and works in
all cases.
Also add a simple unit test for this case, which would have previously
failed, but passes now.
Closes#22592.
Closes#22595.
Translate macOS menu item strings
Translate system cursor names
Translate font weights
Change translations of msgids "KP_F" and "KP_" to be the same as those in locale/es.po
Translate other new untranslated messages
Don't leave a gap between the left border and the paper itself and make
the right and bottom border of the same size.
This basically reverts the changes of ed880dd (New PostScript code,
1998-12-05) -- better 25 files later than never.
Closes#22582.
Unsurprisingly, this doesn't work at all with CHM, so allow disabling
using the custom theme when doing it by adding more custom variables.
Using (multiple) variables for this is rather ugly, but we already use
them for other options, so it seems better to keep adding them rather
than using some other mechanism.
Adding a different custom header file is even uglier, but it seems to be
the only way to avoid including the theme JS files into CHM.
This reverts changes to zh_CN.po done in d4f5b00a8c (Final zh
translations updates for 3.2.0, 2022-07-01), as they accidentally
reverted some of the correct changes done previously.
Import the theme files into a subdirectory without any changes, even not
removing the trailing whitespace, to facilitate updating them in the
future. Do not add the theme as a submodule as it's surprisingly big
(~12MB) and we don't want to spend extra time on cloning it in each of
our CI builds.
Using this theme gives a nicer appearance and supports the often
requested dark mode.
Remove all colour-related options from the existing custom CSS file as
they don't work well in dark mode.
Also switch to using SVGs with transparent background, rather than PNGs,
for the class diagrams, to avoid background colour mismatch in dark
mode.
This fixes the problem with empty descriptions in the annotated class
list and is a prerequisite for using custom CSS theme in the upcoming
commits.
Closes#22288.
Turn off syntax highlighting entirely because using ".xml" here results
in total garbage in output for some reason (while not using any specific
language uses C++ highlighting which is confusing).
This doesn't work under FreeBSD, even if the file exists there.
Show the existing libc candidates on such systems to see if any of them
look plausible.
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.
We need to pass the physical size, not scaled by DPI, as the "size"
parameter of GetBitmapBundle(), so that a user-defined art provider
could use it to select one of the available bitmap sizes (which will
then be scaled, if necessary, by wxBitmapBundle itself).
This change is not 100% backwards-compatible because, in theory, bitmap
sizes could be specified using dialog units previously, but this is not
supported any more. However in practice this never happened because it
simply doesn't make sense to use dialog units for the bitmap sizes and
it doesn't seem worth complicating the code by adding another XRC type
of "DPI-independent pixels that can be expressed in dialog units",
especially considering that DUs are DPI-dependent by definition.
See #22584.
Installing this package directly fails because of a conflict between one
of its dependencies and the already installed libc++-dev which depends
on another, incompatible, version of the same library.
Work around this by installing libunwind-dev directly, which is enough
to make apt uninstall libc++-dev and libunwind-14-dev that it depends on
instead of just stopping with an error.
It's not really clear how are we supposed to use clang with libc++ in
this environment, but this at least allows to build with gcc.
Use existing path for libc.so on Linux/x86_64 platforms to prevent the
test from just exiting without doing anything.
Also don't give a compilation error for unknown platforms, just a
run-time warning is sufficient.
Vadim Zeitlin
MikeWang000000
James Pan
Mark Harfouche
Tim Stahlhut
PBandVadim Zeitlin
Andriy Byelikov
taler21
Ronny Krüger
Paul Cornett