Rick Brewster

You do realize you linked to a bunch of photographs, right? Those nebulas actually exist ... ergo, try search for "nebulas" on Google/Bing image search

You're using XP, or Vista without the Platform Update, or on Win7 RC. In which case Paint.NET is using the GDI text driver; GDI+ was removed for (major) stability reasons. If you upgrade to Win7, or install the Platform Update for Vista, then Paint.NET will use DirectWrite and the text will be awesome.

Yeah, it shows up in the layer box. Wasn't really intentional, but not really a problem either.

This isn't an issue -- it's behaving exactly as designed. There is no setting for the default save type.

You're welcome

I'll e-mail Evan and see what he has to say.

Should be fixed for the next update.

Go to Start, Run, then type %LOCALAPPDATA% and press Enter. From the Explorer window, copy and paste the path to that directory and post it here.

Bug filed. Probably just need to suppress a UI paint cycle in there somewhere.

You might start by saying what DPI stands for

Please, just post updates in 1 thread instead of creating 1 new thread for every update. Also, you really should use IndirectUI -- just derive from PropertyBasedEffect. It's very simple. Right now you can't even press Escape to close the dialog, the tab order is completely random, etc.

Sounds like a simple oversight -- I can have this fixed for 3.5.1.

It isn't a solid line. It isn't an issue. It's working exactly as intended. It only looks like a solid line when it's on a pure-white or pure-black background.

And, if you'd like to try out the fix, install this: http://www.getpaint.net/files/zip/test/ ... nstall.zip It's not an official beta build or anything; it isn't digitally signed, and isn't available anywhere other than via that link.

I think I have a fix for the high CPU usage issue. I'm reverting back to the code that I used for Paint.NET v3.36. In v3.5 I was trying out a new asynchronous code model and it hasn't really proven itself to provide any real benefit. So, it's out (for the upcoming v3.5.1 update). For the issue where Paste into New Image is giving a "invalid format" (etc.) error, I figured that out too. Turns out that the code does this: 1) looks for an image on the clipboard, 2) creates a new image of that size, 3) calls the normal Edit->Paste command to finish up. The problem is that at (1), it was only looking for a bitmap/DIB, and not the other two formats that (3) allows (that is: EMF, and a special Paint.NET internal format that has a selection mask).

Or just general I/O caching during the same session. If it's too slow, then ... to be honest ... it's probably time for a CPU upgrade. I highly recommend making the jump to at least a Core 2 Duo and a 64-bit version of Windows 7.

See this thread: viewtopic.php?f=46&t=31871 Also, moved to Troubleshooting

I am still unable to reproduce this. People have reported issues with pasting from Office (didn't say what version, I've tried 2003, 2007, 2010), and Greenshot. It never reproduces for me, whether it's on my Core i7 or a Core 2 Duo, or with thread affinity set to 1 CPU, or in a virtual machine, or in Win7 or XP or Vista or anywhere. Theoretically the CPU usage issue sounds like a classic inversion-of-priority issue. But that would require a spin-wait loop on the UI thread, as well as code that mucked with the thread priority. But, all threads involved in this should be at normal priority.

This is just what Windows is doing, in XP. This is not a Paint.NET-related behavior, and I'm not even sure if it's a bug (it could be though, I just don't know). Previous versions of Paint.NET had a hack whereby it would "force" thumbnail mode to always be used. By popular demand, and because I no longer use XP (and thus have no concern over the matter), I removed that in Paint.NET v3.5.

Try using Process Explorer to see the tree of processes, and find out what's launching the msiexec.exe's in the first place. Although, depending on how things are launched, this may not reveal anything useful. Anyway, this isn't a bug with the Paint.NET installer. It's doing what it's supposed to be doing.

Why're you bumping after an hour? Contrary to what you may think, we are not sitting in front of our computers clicking 'Refresh' every 30 seconds waiting for your post ... Also, moving to the Troubleshooting section.

You have to upgrade to Windows 7 RTM. Otherwise Paint.NET will not be able to use DirectWrite, which will give you much better text. DirectWrite is not enabled for Windows 7 RC, for stability reasons.

This will be fixed in the next update.

No. Do NOT do that.

If you have a slow CPU then it's possible this particular function will be slower. The reason is that Paint.NET is applying GZIP compression to the history files, instead of relying on the file system's (NTFS) built-in compression (which is fast, but doesn't work well vs. GZIP). This results in much lower disk space use and less disk I/O, but at a cost of more CPU time. For most systems it will be a net positive gain, with respect to performance (either for fast CPUs, or slow disks -- and most disks are slow). Using less disk space also improves reliability, because Paint.NET does not handle running out of disk space (it'll crash).