Rick Brewster

Well it could be something you've changed in your NVIDIA control panel. I'd first look there for anything non-default. The lag is likely not Paint.NET specific, and will probably happen in any other application with similar technology characteristics. Direct3D / Direct2D, runs in a window, in particular. MSPaint and Paint.NET are about as far apart, technologically, as is currently possible ... I would not compare them.

G-Sync windowed mode is known to cause all sorts of problems with everything, including Paint.NET.

It's pretty common for a brand new Win10 installation to first need a lot of Windows Updates to be installed. Catch up on all of that, which honestly could take awhile, and then install Paint.NET. Also you'll often run into trouble installing things like Intel or NVIDIA drivers, too ... it's beyond frustrating when the network card's driver refuses to install because you don't have the newer Win10 build installed. Hello, that's what I was planning to use to download the updates ... 🙄

It's kind of hard to test Paint.NET with settings that can only be obtained by editing the registry, especially since there's no documentation from Microsoft, no support from them, and the fact that these things can change or be removed with any update with no warning or acknowledgement. I've only developed and tested with what you can get by using the Settings and Control Panel. Only a very small number of people are doing this, and so the priority of looking at this is not high. So yes, you could say this is a "bug" but not really. You're hacking the registry to get Windows to do something that it's not really supposed to do, that it's not tested to do, that might not even work, and that would take away time from much more important things. If you can find me with some kind of developer documentation, even some blog post, then I might be able to look at this in the near-term. Something with actual working code. But I'm not going to spend hours tracking down anecdotes from people who're just hacking registry keys and posting their findings.

Paint.NET uses DirectWrite, and that plugin is almost certainly using GDI+. They have different typography systems, so there are going to be differences between them. DirectWrite, for instance, doesn't support bitmap fonts like Terminal. I don't know what Vrinda is, but maybe it's a bitmap font.

No; however, you can use Edit -> Copy Selection and Edit -> Paste Selection -> Replace to make this much easier than it used to be. You can even paste the selection into Notepad if you need to hold on to it (it's just numbers).

We need the crash log itself, not a screenshot of the crash. Otherwise we're all just guessing and flying blind. Please click the "Copy to Clipboard" button and then paste that into this thread.

Those registry settings look correct to me. Are you using portable mode by any chance? If so, settings will be placed into a JSON file next to the PaintDotNet.exe, and will not be in the registry

It's not even an unsolved Windows bug -- it's an unsolveable Windows design flaw. The clipboard can take data in many formats, including bitmaps, sometimes called DIBs (Device Independent Bitmap). One of the properties for a bitmap is the pixel format, e.g. 8-bit indexed, 24-bit RGB, or of course 32-bit RGBA. The flaw is that the DIB format does not include any way to specify the format of the alpha channel: is it premultiplied, or straight? Some apps put content on there as premultiplied, others as straight, and apps like Paint.NET kinda just have to guess or infer. If there's also a PNG on the clipboard then it's unambiguous and things work fine, but DIBs are just flawed and will never work 100% of the time. As @null54 pointed out, Firefox needs to put a PNG on the clipboard, or a link to a file containing a PNG. Also, as a corollary, DIB is the same binary format used by BMP files. This is why Paint.NET does not support 32-bit BMPs with alpha: because there's no information to tell it how to interpret the alpha channel.

Windows 8.1 does not have the Store The error does look like a missing/corrupt .NET Framework kind of thing, so I'd start by installing/repairing that. Getting all of the Windows Updates installed may be right remedy, in fact

Nothing I said would change how the program behaves for you as the user. It would all be ... *wait for it* ... transparent.

There is a way, and I even know what to do and (mostly) how to do. It just hasn't been implemented yet, and it'll be a rather large project. Parts of this have already been completed with each major update to Paint.NET. For example, the version 4.0 release finished what was necessary for the "back end" of the rendering engine (4.0 was a 5 year project). Now the "front end" needs to be updated, which is where the layers are stored. Each layer is currently stored as 1 monolithic bitmap allocation, and the final work will be the break this into tiles. So for each (e.g.) 128x128 pixel region, if it's empty (or just homogenous -- same thing) then only a few bytes of memory will be needed. Storage isn't even the difficult part. It's making sure all of the other parts of the various rendering systems are able to deal with this. There's already quite a lot of work queued up for 2019, so don't expect this soon. However, as you can see in my blog post, development velocity is greatly accelerated now.

Also, you can't bundle Paint.NET with your software. If the user already has it installed, great, go ahead and link up to it -- but you cannot bundle. But yeah you'll only be able to save to a temporary file on disk and have Paint.NET open that. There's no IPC or other mechanism for getting an image into Paint.NET.

Not a bad idea. It wouldn't be hard to implement, although the exact UI gesture would need some work because Ctrl+Click at any time is a bit too overreaching. Discoverability would be an issue, but that's always going to be hard.

What about adding more memory to your laptop? 16GB will probably help a lot

Then Firefox must've changed how they do this. I'd report the bug to them.

If you don't have the Dark theme then you're using a very old version. Install the latest version, problem solved.

You can also adjust the dpi (aka resolution) from Image -> Resize. A higher value will result in larger text (in terms of pixels).

Edit -> Erase Selection, whose keyboard shortcut key is .......... Delete. Please make sure to explore the menus before claiming functionality is missing. You'll find all sorts of great stuff!

Thanks for the info Maybe it'll be helpful, we'll see I also see this behavior when using a mouse on a desktop PC, so the problem may be beyond what you describe. Or it may be in conjunction with it. We'll see ... hopefully there's a reasonable fix.

Yeah you should work with @taoyue to get a feature integrated. Otherwise I can't let you publish this here as an "official" 2.5.1. I've removed the download link from your post. You two can work together to figure out what to do, but the final call is @taoyue's as far as what gets published here with his code.

Look, if you're not willing to install updates then you shouldn't assume things will keep working or be even be safe. That's just the modern reality of software. And if you don't trust Paint.NET enough to enable its updater, then you just shouldn't be using Paint.NET. And that applies for other software as well.

🙄🙄🙄🙄🙄 Have you actually looked at Photoshop's system requirements?! https://helpx.adobe.com/photoshop/system-requirements/earlier-versions.html

I have no idea what this is, but Paint.NET doesn't work on Linux

Also, from a batch file you would use start paintdotnet: There's some more discussion over here where it was troubleshooted recently: