Rick Brewster

Tool plugins aren't currently possible. A big theme for PDN 4, however, is extensibility. Not promising tool plugins necessarily -- it's still a long ways out.

I'm not even sure why I still have the splash dialog, honestly. The current behavior is there because I saw the app taking longer to start up when also opening an image (duh ). Now, it's not so important when the app only takes 1 second anyway.

Or you might have been out of disk space, or your hard drive is dying. You should probably check on both (for the latter, do a search for "chkdsk").

selnessongs, You should go read the rules. No necroposting. This thread's been quiet for 3 years. Thread Closed

Sounds like some kind of disk corruption? In any case, why not just rename the PdnSetup directory. Say, call it PdnSetup_

No.

Paint.NET vs GIMP ... http://www.techairlines.com/gimp-vs-pai ... < no swearing >-flyer/ Paint.NET wins, with 23.5 "points" versus 19.5 for GIMP. I think he added the points wrong -- should be 23.0 vs. 19.5 if you actually add them up yourself. Oh well

Then we'd end up with 25 stickies, one for each thing that people were ignoring and that they'll no doubt continue ignoring. People don't read. It's just the way things work.

Not gonna happen.

How does it show up in other apps' Open dialogs?

rickcf, No need to be grouchy ... wow. This is something that happens because of how Windows XP does things, not Paint.NET. Paint.NET used to force the dialog to always show thumbnail view. Everyone yelled at me about it. Since I no longer use XP and thus don't care, I removed that behavior. I do not know why XP is forgetting your preferences. I'm sure if you open that folder in Explorer and set it up how you want, it'll remember (or not ). Win7 and Vista work as expected here.

And remember what I said about asking questions that you don't even need the answer to, jerry533482? You're starting to get on people's nerves. Thread Closed

Development spanning 2 decades and it's in alpha. Yeah I'll get right on that .... Windows is so expensive* that they need to roll their own version of it from scratch. * not

Geez, It's A Crash In CustomBrushes Maybe You Should Report It There Thread Closed

Sorry, but I'm not going to be updating this plugin at all.

PLEASE STOP SHOUTING. Thanks.

This is something I was looking at for Paint.NET v3.5. WIA supports it if the hardware and driver support it, but I just didn't have enough time left over for it. On the app side, it's really no more difficult than File->Open with multiple images.

You may not do this. Paint.NET may not be used within your application. Thread Closed

You won't be able to install Paint.NET v3.5+ in that case. I'd say you're due for an upgrade though Get a Intel Core or AMD Phenom, and a copy of Windows 7 ... things will be quite nice!

Please don't speculatively answer a question like that, Wilson.

Make sure that you've installed all the updates for Visual Studio itself. There was one released last fall which was very important, but that doesn't seem to be ubuquitous yet. It affects the Visual C++ Runtimes, and that's probably what's causing this issue. Basically, Paint.NET is installing a newer version of the C++ runtimes than Visual Studio (that is, the not-updated Visual Studio) is able to deal with.

Moved to Troubleshooting

What CPU do you have? Paint.NET is using the Windows function IsProcessorFeaturePresent(). So if Windows doesn't think you have SSE, then Paint.NET won't either. If Paint.NET v3.5.1 worked, then v3.5.2 should also work.

There's no way to get Paint.NET to auto-execute something like Ctrl+Alt+V. You'll simply have to do it manually. In other words, there's no /pasteIntoNewImage command-line parameter.

Well another idea I had was to calculate everything in the background as you moved the mouse, drawing something analagous to a contour map. Each shade of blue would correspond to a different tolerance value. There's clearly room for innovation here, it just has to find a spot amongst all the other priorities.