e13b4f8833
The old code in wxToolBarBase::AdjustToolBitmapSize() forced the use of the exact value of the requested bitmap size multiplied by the current scale factor, which resulted in ugly bitmaps whenever fractional scaling factor was used. It also used not immediately clear IncTo() call. Simplify and improve it by handling the cases when we have a requested bitmap size and we don't have it differently: if we do have it, just use it directly, but only with an integer scale factor. And if we don't, then simply use the bitmap size suitable for the current scale factor. This seems to result in the most expected behaviour and, notably, doesn't break the toolbar sample where the bitmap size can still be toggled between small and big bitmaps on both normal and high DPI monitors. Also update the documentation: still recommend not to use SetToolBitmapSize() at all, but don't claim that it forces fractional scaling, as this is not the case any longer. |
||
|---|---|---|
| .github | ||
| 3rdparty | ||
| art | ||
| build | ||
| demos | ||
| distrib | ||
| docs | ||
| include | ||
| interface | ||
| lib | ||
| locale | ||
| misc | ||
| samples | ||
| src | ||
| tests | ||
| utils | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| appveyor.yml | ||
| autoconf_inc.m4 | ||
| autogen.sh | ||
| CMakeLists.txt | ||
| config.guess | ||
| config.sub | ||
| configure | ||
| configure.in | ||
| descrip.mms | ||
| install-sh | ||
| Makefile.in | ||
| mkinstalldirs | ||
| README-GIT.md | ||
| README.md | ||
| regen | ||
| setup.h_vms | ||
| setup.h.in | ||
| version-script.in | ||
| wx-config-inplace.in | ||
| wx-config.in | ||
| wxwidgets.props | ||
| wxwin.m4 | ||
About
wxWidgets is a free and open source cross-platform C++ framework for writing advanced GUI applications using native controls.
wxWidgets allows you to write native-looking GUI applications for all the major desktop platforms and also helps with abstracting the differences in the non-GUI aspects between them. It is free for the use in both open source and commercial applications, comes with the full, easy to read and modify, source and extensive documentation and a collection of more than a hundred examples. You can learn more about wxWidgets at https://www.wxwidgets.org/ and read its documentation online at https://docs.wxwidgets.org/
Platforms
This version of wxWidgets supports the following primary platforms:
- Windows XP, Vista, 7, 8, 10 and 11 (32/64 bits).
- Most Unix variants using the GTK+ toolkit (version 2.6 or newer or 3.x).
- macOS (10.10 or newer) using Cocoa under both amd64 and ARM platforms.
Most popular C++ compilers are supported including but not limited to:
- Microsoft Visual C++ 2005 or later (up to 2022).
- g++ 4 or later (up to 12), including MinGW/MinGW-64/TDM under Windows.
- Clang (up to 14).
- Intel icc compiler.
- Oracle (ex-Sun) CC.
Licence
wxWidgets licence is a modified version of LGPL explicitly allowing not distributing the sources of an application using the library even in the case of static linking.
Building
For building the library, please see platform-specific documentation under
docs/<port> directory, e.g. here are the instructions for
wxGTK, wxMSW and
wxOSX.
If you're building the sources checked out from Git, and not from a released version, please see these additional Git-specific notes.
Further information
If you are looking for community support, you can get it from
- Mailing Lists
- Discussion Forums
- #wxwidgets IRC channel
- Stack Overflow
(tag your questions with
wxwidgets) - And you can report bugs at GitHub
Commercial support is also available.
Finally, keep in mind that wxWidgets is an open source project collaboratively developed by its users and your contributions to it are always welcome. Please check our guidelines if you'd like to do it.
Have fun!
The wxWidgets Team.