Rick Brewster

Well gosh I mean we now have dual core 3ghz processors and 64-bits and stuff, why the heck shouldn't we take advantage of it.

RaveN, chill the heck out man. This is your only warning.

For the gradient I plan on making it more "wysiwyg" than Photoshop. In PS you have to draw a line and then let go of the mouse button before it renders anything. I find that to be a nuisance, and am going to implement it so that it draws the gradient in real-time as you're moving the mouse.

Right now the guaranteed features are MDI and the improved Colors window that I described in another thread. There are also lots of little things that I can't even remember without pulling up the list of resolved bugs and work items. The other feature I am planning on, with the highest priority, is a gradient tool. And remember, any features not in 3.0 aren't cut. They're just shoveled into the bucket for the next release.

Allright fair enough, I usually don't have time to read things in full so I may have said that based on a quick perusal. Anyway, one thing that I ask you to realize is that Paint.NET is a spare time project. I unfortunately have very limited time to work on it, and so progress is slow, but assured. Any current release of Paint.NET is also not the final destination of the project: I subscribe to the "release early and release often" mantra for Paint.NET. It's better to have imperfect stuff in user's hands that they can use and provide feedback on right now, rather than wait 5 years and provide something perfect to an audience of zero. Paint.NET isn't perfect or complete, and I try to ensure that I don't make claims of that kind. Crazy Man Dan, forum regular (and now a moderator) is often seen here on the forums recommending other software to get things done. Which is fine. I'm fortunate enough to be in a position where I don't have some squash-the-competition and take-over-the-market business plan or requirements. If I working on it full time you would see some truly amazing things, trust me

Yeah but you gotta give me a moment to be a smartass v3.0 has a soft date of December. I will cut features to make that date. Right now it's converging quite well towards a first milestone, and then after that I plan on adding a very small handful of features, releasing 3.0, then shoveling the remaining features in to v3.x releases.

Paint.NET v2.0 was released December 2004 ...

Just like I predicted ... ! Get it via the updater (File -> Updates -> Check Now), or from the website, http://www.getpaint.net . Changes and new stuff: * New effect: Zoom Blur * Fixed: DPI was not being saved or loaded correctly for file types other than PDN and JPEG * Fixed: Text Tool now works with Alt+#### special character entry without moving the cursor * Fixed: Loading PNG images with alpha was often resulting in incorrect, off-by-1 color values

I created an off-topic area, and made Dan a moderator

Layers menu -> Import from File or just drag-and-drop files from explorer

No plans to do so.

You can get it through the built-in updater right now. It's making its way to mirrors and then the rest of the website will be updated as well.

With all due respect, this would absolutely not be "easy" to add. I'm all for it too, but stop being a conceited jerk. This is your only warning.

Make a new layer, type the © symbol, then adjust the layer's opacity

No problem I just wasn't following the discussion very well

I didn't say there aren't people here. Just because you're on the forum a lot doesn't mean you should be a moderator. Don't ask to be a moderator. It doesn't work like that.

You guys aren't making any sense. Stay on topic.

Paint.NET supports Tablet PCs (the special laptops).

Well I'd need someone(s) who could moderate fulltime. This forum is already bulging at capacity in terms of my ability to keep up and moderate!

Hmm, well Paint.NET doesn't have any batch processing functionality at this point. So this might not really be a task well suited to it anyway, with or without the bug or workaround

I don't believe so. This would require an algorithm where it would try to save the file, and then if that failed it would step through each piece of metadata and try saving the file with only that part of the metadata. It would then catalog which metadata caused the codec to freak out, and then it would save the file again without those pieces of bad metadata. Very bad for performance (imagine saving over to a network share) and it's still just guessing with no guarantee that it would even work. Honestly the workaround is hardly complicated as you can do the entire thing with the keyboard, which is why I listed the shortcuts. Ctrl+A, C, N, V. Well, press enter after Ctrl+N.

In the app, go to the menu ... Help -> Help Topics

I think there are plenty of those elsewhere on the web.

Moved to General Discussion Please post in the correct forum. The Plugins forum is reserved for plugin publishing only.

Ok Dan, the 2.72 release this weekend will not have a fix for this. It's simply too risky to fix in the stable 2.xx branch. It will include a fix for DPI not saving/loading correctly for anything but PDN and JPG files (the fix for which I stumbled upon because of this post!), so all is not lost. As a workaround, the customer you are working with should be able to do the following: 1) Open the TIF file in question 2) Resize as you normally would 3) Edit -> Select All (Ctrl + A) 4) Edit -> Copy (Ctrl + C) 5) File -> New (Ctrl + N) 6) Edit -> Paste (Ctrl + V) 7) Now save as whatever you want. Essentially this will strip all the metadata out of the image so that it will save correctly.