Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Turns out the high DPI image support introduced in #557 had some significant issues - most notably, it was rendering crisp high-res images, but wx then decided to upscale them *again* if your DPI scaling was set to 200%. To fix this, we need to move to wx.BitmapBundle. This is intended to be used by bundling multiple versions of the asset and sticking them all into a bundle, then having wx choose the most appropriate resolution. Or use an SVG, statically render a bunch of sizes and stick them all in a bundle. We don't do that and instead dynamically create them, sticking only a base resolution asset and the actual version we need in. That way wx will use the higher-resolution version without applying its own scaling. This does of course look ugly with checkboxes and such, but those are temporary anyway - #511 will replace them with SVGs. Note that we now pass in iconSize for (nearly?) everything, so maybe we should just make it a required parameter. Under #511, #557
- Loading branch information
Showing
5 changed files
with
56 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters