Rick Brewster

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.

Ok, I've fixed this. You'll see this working normally in the 2.72 release by this weekend. Illnab1024, I have no idea what your post means or is referring to.

4) Your screenshot on the Effects page shows a bunch of additional effects that don't come with Paint.NET. (Drop Shadow, Condition Hue/Saturation, Gradient). The help file should not include these!

1) Please don't package the ZIP file that way with an embedded C:\Programmer\Paint.NET path. None of the other language packs do that, you'll just confuse people even more. 2) There are many pages in the help file that are still in English (unattended installation), or that are translated from the v2.64 version of the file (like the system requirements, and the copyright tag at the bottom of every page). 3) Why is there additional text at the top of the License.html file? What does it say?

you just can't. I think there's no free Windows C/C++/C# compiler because Microsoft surely want royalties to accessing Windows.Forms & Microsoft Foundation Classes (btw others). No Troll please. Bob, you are incorrect. You are trolling. Stop.

Moved to General Discussion Please post in the correct forum. Notice how the top of the Tutorials forum has a post that explicitely states that it is for tutorial publishing ONLY.

Why the heck would that be a resource language problem

Sounds like an easy fix actually. ... Don't process arrow keys when Alt is held down.

I've considered various business plans, ranging from charging even just $1. In the end, it's really just simpler to give it away for free and ask for donations and use the Google AdSense. So that's how I'm keeping it for now. I make less money this way but it's more fun I guess. It really does keep it simpler for a myriad of reasons.

Yeah I've been looking at this in the debugger, there is definitely some EXIF tag that is causing our JPEG saver to freak out (it's based on GDI+, go figure). The question is now how to mitigate this. On another note, I think I figured out why saving as a PNG doesn't save the DPI setting, and I may be able to fix it.

So use the built-in security systems of Windows and don't give any of your users Administrator privilege. Then the menu items will be greyed out.

No. I fired Dennis. Tom is super busy but does manage to contribute here and there (Zoom Blur is by Tom). I am also super busy but have some weird addiction to keeping the project going.

*shrug* No idea.

I find the PowerToy works great.

Fair 'nuff. I have no idea if SharpDevelop will work. Probably won't since we also use the C++ compiler for a few things.

There's an entire help file you can read through ...

Layers are your friend. Paint.NET provides much more sophisticated means for doing anything that MS Paint ever wished it could.

I don't ever remember promising such a tool.

Cool plugin, might have to look at adding something like this for a 2.7x update Is that Rachel Bielson? I can think of only positive things to say about her ... ha!

Raven, stop thread crapping with PNG vs. JPG rants.

Thanks! I have posted this in the language pack download thread here, http://paintdotnet.12.forumer.com/viewtopic.php?t=538