Rick Brewster

Yeah I've actually noticed this too, but haven't been able to figure it out. It seems to only happen on some people's systems, especially those who do development-related "stuff".

If a JPEG has an embedded thumbnail, Paint.NET doesn't remove it or update it. Known bug. The image itself is correct.

Have not seen this, nor heard any other reports. "Chewing through my RAM" is pretty vague. Was Task Manager reporting a lot of memory usage, was the hard drive grinding away, or ... ? XP, Vista, Win7 .... ? Was this during installation or after Paint.NET relaunched ... ? etc. etc. Oh, and ... moved to Troubleshooting

I suggest adding a "link sliders" option like you see in the Posterize adjustment. With IndirectUI it's easy

I've just filed a bug for v4.0 to address several improvements that should be made to the Line/Curve tool: the ability to change the # of nubs, and granular history. In your case you'd just set the # of nubs to 2 and have at it. (Yes I'm sure I had a bug filed for this already, but at some point I went through and killed off all the bugs/ideas that'd been sitting around for forever in my database. If features are good ideas, they'll come back to you. Like this one.)

Yeah I only meant it as a joke Kinda like this, my new favorite picture of the day ...

I've also filed a bug, for v4.0, to make that "(error)" a lot better. Like a + button to give you the exception details or something. I've been meaning to do that for awhile but I always have had other things take priority or attention.

Ok well that was easier to fix than I thought ! ... just had to switch to using 64-bit accumulators instead of 32-bit ones. Now the error can still happen, but you'd need an image about 50,000x larger. I'm ok with that, especially since the hard limit is 65,535 x 65,535 pixels. I tested on a 16,000 x 16,000 image and it worked fine (it was a blank/white image like described above). Attached is a zip with a new PaintDotNet.Data.dll and .pdb file. Unzip to where you installed Paint.NET (usually C:\Program Files\Paint.NET). Be sure to say yes/ok/confirm when it asks to overwrite the existing files. PDN.Data.3.55.QFE.33944.zip

It's an unchecked overflow (which is by design for some parts of the code) that's then turning into a real error. For now just save smaller images I guess ...

Ok this is pointless. Thread Closed

So basically you did what is described over at the big capitalized sticky post in this section of the forum, viewtopic.php?f=10&t=854

Reproduces here too. I'll look into it.

Maybe he typed it into Notepad by accident :?:

Or the Escape key ...

Sounds like it's just your computer. I've certainly never seen that happen, or had anyone else report it.

It depends on the resolution you've set in the image. DPI = dots per inch (pixels per inch) 96 DPI = 96 pixels per inch. By default, Paint.NET creates new images at 96 DPI. Use Image->Resize to check the DPI (resolution).

Older versions are neither supported nor available, and the rules are very clear about this. Please don't ask again. Honestly, CPUs with SSE support are hardly bleeding edge hardware. CPUs without SSE are simply too slow to be very useful, and are very cheap to replace.

I run the PDN installer while VS is running all the time. No issues. This has happened to other people though and has nothing to do with 3.5.4. (that is to say, it has nothing to do with the code changes in this particular update) Like I said, make sure you have all the updates. There's one in particular that came out last year -- you have to make sure you have the Visual C++ 2008 Redistributable version 9.0.30729.4418, as well as the updated VS2008 that actually uses that instead of the older version.

Mumbly, everything's working fine here with VS 2008. Make sure you have all of VS 2008's updates installed, starting with SP1. There were a few that came out last year that many people still don't have. Go to Windows Update and make sure to opt-in to "Microsoft Update," which will ensure that non-Windows updates get installed automatically as well.

The current version of Paint.NET can't be used for batch processing. Sorry.

PLEASE STOP SHOUTING. Welcome to the forum, but please read the rules first. You'll need to edit the title of your thread asap.

Paint.NET cannot cause a BSOD. Only kernel-mode code can do that. You will have to troubleshoot this with the Nero guys, who probably do have a kernel-mode driver installed. Also, only the latest version of Paint.NET is supported, which currently is v3.5.4. We cannot help you with v3.22.

Glad it works though ...

What BoltBait said. This isn't a Paint.NET issue. Thread Closed

The user account will always have file system access to a directory that applications are told is "the desktop." Whether or not the shell is configured to actually show the desktop itself is another matter.