Rick Brewster

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.

No features have been added or removed in v3.5.6.

If the font won't work then there's nothing I can do about it. If you're on XP then you might try upgrading to Windows 7, or Vista (with SP2 and PlatformUpdate), at which point DirectWrite will be used instead of GDI for the Text tool and font list. DirectWrite is generally better when it comes to font support and rendering quality.

A Pentium 4 with only 512MB RAM is pretty much at the bottom of the barrel in terms of system capabilities at this point.

Also try running PdnRepair.exe from the Paint.NET installation directory (usually C:\Program Files\Paint.NET), if it still persists after pyrochild's suggestion.

Doesn't repro here either.

Already posted, http://forums.getpaint.net/index.php?/topic/16432-stringsresx-for-paintnet-v35/ The resx has not changed since v3.5.0.

If the window positions aren't being remembered, you could have an issue with the security/permissions settings on the registry key where Paint.NET stores its stuff. HKEY_CURRENT_USER \ Software \ Paint.NET Delete the thing. If there's an issue writing the window position values there, Paint.NET will silently skip past it ... instead of crashing.

That text is invariant. Translations can't change it. That is on purpose, as per legal guidance.

I can't repro this. Can you get me some very specific steps that will always reproduce this?

MirithKailyn, please post in the Troubleshooting section. Thanks.

What does the change log say? http://www.getpaint.net/roadmap.html

Please post a screenshot.

There's another thread on this somewhere. Summary: not ever gonna happen.

It will be positioned to fit within the viewport. This is by design. It's not a bug, but it is different from v3.5.5 and earlier. If you always want the pixels to paste into the same spot, you can zoom out (Edit -> Fit to Window, Ctrl+Shift+B ).

If you're going to continue being cranky and argumentative then there's no reason for us to try and talk you down. You've got the facts, now go use them in a productive manner that doesn't waste our time. Thread Closed

Moved to Troubleshooting

Bah... showoff!

Works fine here. Press Refresh or clear your cache or something. And like it says above,