![]() Credit goes to Bruce Bowyer-Smyth - Fixed: Addressed CVE-2018-18447. The error message will indicate this cause - Fixed: Addressed CVE-2018-18446. To launch the Store version with hardware acceleration disabled, go to Start -> Run and type in "paintdotnet:/set:UI/EnableHardwareAcceleration=false" (without quotes) and press OK - New: Added detection for when "Diebold Warsaw" is causing Paint.NET to crash. This is also necessary for the Store release whose virtualized registry cannot be edited. This is specifically useful for disabling hardware acceleration if the app won't start or you can't reach the Settings dialog. "* Bicubic will be used," weren't going away or updating correctly - New: Added a /set:SETTING=VALUE command-line parameter. They were "too dark" in translucent regions - Fixed: For the Store release, launching with the paintdotnet: protocol no longer shows an error if no parameters are provided - Fixed a crash for some effects that were rendering too quickly - Fixed a bug in the Image>Resize dialog where the asterisk and the note about which resampling mode was being used, e.g. More optimizations are coming in the next update - Fixed: Pixel grid no longer draws some dots darker than others at some zoom levels - Fixed: Radial Blur was not handling alpha correctly - Fixed: IndirectUI ColorWheel swatch is now rendered correctly (without the fading alpha gradient) - Fixed: The tooltip describing the shortcut key for tools now indicates how many times to press the key (e.g., press S four times for Magic Wand selection) - Fixed: Pressing Escape to deselect now works with all tools (this bug was introduced in v4.0) - Fixed: Images with variable alpha were not displaying correctly at some zoom levels. ![]() Improved startup performance if "a lot" of effect plugins are installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |