Rick Brewster

If nobody reports crashes... I won't know about them. Can't fix them.

System.TypeLoadException: Could not load type 'PaintDotNet.PdnFileTypes' from assembly 'PaintDotNet.Data, Version=4.201.7158.31906, Culture=neutral, PublicKeyToken=null'. Looks like it's trying to access a class that it shouldn't have been, which has since been moved. The plugin will need to be fixed.

This is way too much to read, I don't know why there's so much text here. tl;dr yes I know about this, I want to implement it, it's just a complex thing and it's not at the top of the priority list. Not much to talk about really. No need to write a novel to try and convince me.

Yup. You can add apps to an exclusion list, or just turn off that terrible feature altogether.

This isn't a bug, it's intentional. Even actions in the History that have been undone are considered to be "unsaved changes." The only state that is exempt from needing confirmation is when you've opened an image and literally done nothing to it.

Since I don't have PaintTool SAI, I need you to gather some data for me so that I can debug this. See the instructions here: https://forums.getpaint.net/topic/114697-error-pasting-images-from-outlook-in-42-update/?do=findComment&comment=560660 (unfortunately that person never responded ...) So you 1) do a copy operation in PaintTool SAI, then 2) use the instructions above to export the contents of the clipboard to a file, and then 3) give me that file. I can then take that file and import its contents into the clipboard on my system, and then I can look at it and see what Paint.NET may be doing wrong (or what SAI is doing wrong).

By "Sai" you mean PaintTool SAI? https://en.wikipedia.org/wiki/Paint_Tool_SAI

Yeah this sounds like a buggy shell extension, or a mapped network drive to a computer that's not responding very well (overloaded server or bad connection).

No, I'd rather not have it documented. That's intentional.

I dunno what can i say *brushes dirt off shoulder*

The "polishing" that /createMsi does is just baking in MSI properties into the MSI files. You don't need this if you can provide the correct MSI properties on the command-line. The most important one to get started with is USINGWIZARD=1, which is used to steer folks toward using the setup wizard or /createMsi. But if you know what you're doing (TM), it's no big deal to supply it on the command line to msiexec. Other properties are listed at https://www.getpaint.net/doc/latest/UnattendedInstallation.html

Can you zoom out a little and give some context about why you're doing things in such a bizarre manner?

Closing thread. New version incoming.

This is an important update that fixes many issues, including some crashes. It also adds JPEG XR file type support for Windows 8.1+. If you’re using the Windows Store release, you should get the update automatically within the next 24 hours. You can also force an update check by following these instructions. For the Classic release, you should be offered the update automatically within the next week or so. You can get the updater soon by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website. Change log: New: JPEG XR file type support (Windows 8.1+ required) Fixed: Holding Ctrl when dragging a selection with Move Selected Pixels will again leave a copy behind (but only with the mouse) Fixed crashes when saving DDS images Fixed VTF file type plugin. It was not working in 4.2 except for images that were an exact power-of-2 size on each dimension. Fixed: .BMP files can be opened even if they're not actually BMP images (they still need to be a valid WIC-supported file type such as PNG, JPEG, etc.) Fixed very bad performance when opening large images with embedded rotation metadata Fixed various crashes, such as when using File->New or Image->Resize, that sometimes happened if the previous update needed a reboot but either 1) it didn't tell you that, or 2) it did but you didn't reboot Fixed the problem that was causing the need for the aforementioned reboot in the first place (string resources file was locked by the thumbnail provider shell extension) Fixed: Text tool will no longer draw tiny text when an image uses dots-per-centimeter instead of dots-per-inch Fixed menu ordering of effect plugins that have duplicate names Fixed: The mouse wheel may now be used to scroll the Palettes menu in the Colors window (thanks @AndrewDavid for the suggestion and @toe_head2001 for the fix!) Fixed metadata handling that was preventing some images with EXIF tag 330 from being able to load Fixed metadata preservation for old images that pad EXIF string values with null terminators Fixed title bar text color when using certain custom accent colors in Windows 10 Fixed title bar accent color when Tablet Mode is enabled

It's not about difficulty, @avfb. It's about prioritization. There are A LOT OF THINGS to do. Simple as that.

Locking this thread. Final release incoming.

Yay! Glad it works again You might report this to the Windows Blinds folks. Maybe they can fix a bug on their side.

As @toe_head2001 alludes to, this is almost certainly caused by some other software on your system. Software like Window Blinds has been known to cause all sorts of trouble like this.

Probably a bug in the plugin? ¯\_(ツ)_/¯

This is fixed for the upcoming 4.2.1 release. Thanks for reporting it! The conversion from dpcm to dpi was being done wrong. It was dividing, instead of multiplying, by 2.54.

Does this happen when saving any image? For instance, what happens if you start up Paint.NET and try to save the default/blank image? If that works, then maybe something's "bad" * in one of the images you're working on. If that's the case then it would help if you send me one of the images (just reply here and attach the image). * ("Bad" in the sense that Windows doesn't like it... not your fault!)

Yup, by design. Otherwise you can never "hold on" to that original aspect ratio, it gets slushed away in rounding errors if nothing else. Your workaround is the right one, just "reset" the aspect ratio by bouncing it through the clipboard with Edit -> Copy Selection and Edit -> Paste Selection -> Replace.

Same underyling issue (and fix) as this:

Yeah, that's clearly a bug. I'll see if I can get it fixed for the 4.2.1 update that's coming out very soon.

Auto-detect will always include transparency if necessary, by way of choosing 32-bit. You'll only loose transparency if you selected 24-bit or 8-bit. (I think 8-bit also supports transparent, although not varying levels of transparency)