Rick Brewster

For 1-px brush width, without antialiasing, I use my own renderer because Direct2D does a bad job there. So there's precedent for something like this. Every time I've looked at this problem, it just was not simple to solve despite seeming like it should be.

I'll add the link to the github issue where I'm tracking this -- who knows, I may get around to it

It detects it's running in the APPX container and that the package information is wrong. This is to prevent plagiarism on the Microsoft Store, which was a big problem earlier this year.

This is an EXTREMELY bad idea. We cannot help you if you are going to disable updates, even for Windows. It puts your system into a state where troubleshooting just becomes a total nightmare. And, your system will eventually become significantly more vulnerable to malware and other bad things. (This is not theoretical, btw.)

Please post the crash log so I can make sure it’s the same thing

I believe I already have a fix for this which will be in the 5.0.11 update

I don’t even know if you can disable that, at least not officially

Do you have a lot of fonts installed?

Sorry, no, there’s no way to choose which ligature set you want

Paint is probably using GDI, which is the old/legacy API for text rendering, whereas Paint.NET uses the much newer and modern DirectWrite. I'd wager that what Paint.NET is rendering is the correct way to do things.

That sounds like a recipe for total disaster. I'm not going to be changing anything here -- the current state of things is the result of almost 20 years of development, testing, and reactive fixes to how things work in the real world. It works. That's what's important. Any changes legitimately risk causing chaos across millions of PCs. If the disk space is that important to you then you can use command-line tools to establish symlinks between the identical files. I don't promise that will actually work though.

This thread is 3 years old, the conversation was over long ago

No, that wouldn't make much sense. It would mean an infinite number of brush stamps. If you want the default spacing, it's 15%.

AVG and Avast are "known troublemakers". They cause all sorts of problems while not improving your PC's security above that the built-in Windows Defender provides. My recommendation will always be to remove them.

Paint.NET only makes the copy in Program Files\paint.net\Staging. It does this because it was proven to drastically reduce the number of uninstall/update failures. For some reason the other copy, which Windows itself is supposed to maintain, would get deleted. No idea why. And then the user would be left in a completely broken state, unable to uninstall, update, or reinstall. It does get tagged for NTFS compression, which saves about 33%. It's not very large either way on a modern system.

Aha, now I see it

You don't have access to the file for some reason. Nothing has changed in this part of the codebase, so it's not the new update causing this.

It's a lot more than "naming conventions." I just updated it yesterday. You need to fetch/pull the latest commits.

Grammar seems fine to me ......

This sounds like there's a problem over on your end, or with your ISP. Or your DNS cache hasn't updated ... or something. Traceroute works fine for me.

Don't moralize me.

Also this is a good time to point out that I highly recommend migrating away from GDI+ (aka System.Drawing). Paint.NET now has robust support for Direct2D, which also happens to be hardware accelerated. Direct2D is the modern replacement for GDI and GDI+. There is a learning curve, of course. You'd switch from BitmapEffect over to GpuDrawingEffect, and then issue drawing commands in your OnDraw() method to the IDeviceContext that you are given. All of the drawing commands get stashed in a buffer (a "command list", rather), and then Paint.NET does all the work to do tile based rendering, recover from GPU errors (like device removed, driver updated), etc. This is all dependent on how deep into the rabbit hole you're interested in going, of course.

Okay both seem to be working as of right now. 30 minutes ago I couldn’t get www to work. Hopefully it’s fine now …

Should be fine now but do reply again if it's not

Likely a transient error. If that’s the case it will go away in a bit. If not then I’ll file a support ticket with the hosting provider.