Rick Brewster

No. If you want to always have a white background, then leave the 'background' layer as white and always draw on a 2nd layer.

Not gonna happen. NGEN is a best-faith effort optimization. There are any number of reasons why the native images would be missing, and even then it still requires administrator privilege to generate them. It's not an error, it just results in lower startup performance.This is also an overly niche scenario, and in general it's not a smart use of time to optimize for those.

Paint.NET has a 100% proper alpha channel. What it doesn't have is alpha masking (essentially a 2nd alpha channel that's editable by itself).

Well, what kind of system are you running? CPU type and speed, amount of memory (RAM, not hard drive space), and Windows version (XP? Vista? 7? is it 32-bit or 64-bit?) 1) Make sure you're running 64-bit, like BoltBait said 2) Make sure you've got a dual-core (or more) processor. 3) Make sure your system isn't a dinosaur. And, how large are the images you're loading, and how many layers are you using.

Startup time will be slower because NGEN was run with .NET 4. If you have any .NET 2.0 - 3.5 installed, then Paint.NET will use that instead of .NET 4. It's a technical limitation of the version dispatching system. Just rerun the Paint.NET installer and it will re-NGEN itself, and then startup faster.

This is the Paint.NET forum, not the "Name That Font" gameshow. Thread Closed

ruh roh ... You need to run chkdsk. Search here on the forum and you'll find some instructions.

And read the rules. Overly generic thread titles such as "Help Required" are not allowed. And read the license. Paint.NET's license expressly forbids you from incorporating it into your own application.

I don't program in VB.NET either. Paint.NET is in C# mostly, with some C++/CLI, and even some classic C.

It's Segoe UI.

ORA eh? Open Raster Format? Do people actually use that? (Not trying to be denigrating, it's an honest question)

You can accomplish the same things in Paint.NET. Just use layers, magic wand, and Tolerance of 0. For specifics, experiment or ask here in the forum. Or both! Along with resizing the canvas by dragging the corner, I classify that as a "bad" feature of MSPaint: something that got people used to a convenient, but unfortunately far too limited, means of accomplishing tasks. The "vocabulary" in higher-end imaging software (GIMP, Photoshop, and yes Paint.NET) is more sophisticated, but far more rewarding once you learn it.

Moved to Troubleshooting

This is a bug in Hydravision, and not Paint.NET's "fault" -- what you've stated is not a correct conclusion. However, I'm glad you found a workaround/fix.

Sorry, I have no plans to include Persian.

Actually, technically I didn't. Michael Kelsey did, iirc. There was a resources usage problem in older versions of Paint.NET whereby it's allocate 1 GDI bitmap object per history item, even for items that used the same little 16x16 bitmap. After awhile Windows would stomp Paint.NET in the face, "you're using too many!!!" Now it collates all of those, and there's really no reason to have "Clear History." I repeat: there is no reason to have Clear History. It will not save memory or make it run faster. Stop asking for it.

History data is saved to the hard drive, not stored in memory. It is 100% useless to have a "Clear History" button. Memory management is my job, and not something that should be shrugged off into an end-user "feature".

I don't know. I haven't researched the way Photoshop does it versus the way that GDI+ or WIC does it. (Paint.NET uses GDI+ for JPEG encoding. In Windows 7, GDI+ codecs were rewritten to use WIC, thus Paint.NET essentially uses WIC in Windows 7.)

The MSI won't have a good signature because it's modified by the installer. This is normal and nothing to worry about.

Almost half of the development effort that went into Paint.NET v3.5.x was related to fonts. If it won't work, then there's really and 100% honestly nothing more that I can do about it.

Don't use JPEG when fine grain pixel detail is important, such as in the example you gave.

If you want Photoshop, then go buy Photoshop. People don't migrate from Photoshop to Paint.NET. Most people have never even seen Photoshop. Paint.NET does not have "take over Photoshop" as a goal. There are many aspects of Photoshop's UI that I do not like. Why would I blindly reimplement them all in Paint.NET? Also, if you want Gimpshop, then use Gimpshop. Paint.NET's selling point is not, "hey it's exactly like anything else you might have ever used and it bends over backwards to be 100% reconfigurable and stuff." No -- Paint.NET is Paint.NET. That is its selling point.

Usually this happens because you have an buggy shell extension installed, such as DivX which has historically done a super poor job with respect to thumbnail generation.

No. If you open a PDN, then it has full generality over PNG. Defaulting back to PNG would be surprising or unexpected behavior over the long run. Paint.NET flipping back and forth between PNG and PDN all the time for the same file would be obnioxious. Please people, think about how your suggestions would play out over the long haul and not just in your specific scenario. It is not that arduous to think through other scenarios to figure out why things behave in the way they do, nor is it so painful to learn a few other commands in order to get the correct workflow for your needs. Also, this is neither a Troubleshooting nor a Bug Report post. Moving to General Discussion

You're missing the point. The key is that he added layers. Saving as a JPEG at that point would be a data loss bug, which is one of the worst kinds (2nd in priority only to security issues). Saving as a PDN without prompting would be confusing and just as bad. Thus, Paint.NET prompts you. This is not about "simple code because it's free." It's about upholding the principle of least surprise. What's worse? "Woops, my JPG doesn't have any of my edits ... oh, I saved as a .PDN ... but that's ok, because none of my data has been lost. I will open, flatten, and resave!", or ... "Woops, I lost all my layers even though I wanted to go and move them around again, and thus I have lost both the original image and my structured edits to it." No, they're not. You can save as a .PDN to preserve them. Hence the prompting when you add layers. Ctrl+S for Save has never been defined as "save without a dialog." It means, "if possible, save right away, assuming you have all the information needed to do so without causing the user any data loss or undue surprise." You'll notice that even saving a JPEG after opening it will give you the Save Configuration dialog. That's because Paint.NET doesn't know what quality setting should be used for saving it. I can give you a 100% probability that this behavior will not be changing. Ever.