Rick Brewster

Well I doubt it's an actual "out of memory" problem, esp. since you're on 64-bit. You keep saying that "it" says "parameter not valid" but I don't know of any dialog in the program that prints this error. I have no idea what error message you're talking about, and you haven't provided a screenshot, nor am I psychic. You do need to accept that maybe there's something you can do to fix this. Like I said, there is no bug in Paint.NET -- it's just loading a cursor. A crash at that point indicates some other problem.

Yeah it seems like the functionality being asked for amounts to adding on "execute Image->Resize to W x H pixels after I've selected a W x H area using Fixed Ratio", as part of a second Crop-style command. Does that sound right?

*looks at all the DLLs that are loaded* Is it me, or do you have every plugin installed? You also seem to have a TON of other apps that are hooking into the process. For example, "ASUS Data Security Manager", all sorts of "Norton 360 Premier Edition" DLLs, etc. The floating point state is also incorrect ("fps=0x0" on the Processor line, but it should be 0x1). I would try disabling or removing those. This doesn't look like a bug in Paint.NET. All it's doing is loading a cursor from the resource DLL. Something else is corrupting the state of things. Also, if you have an Effect that has crashed, then don't be surprised if Paint.NET falls over shortly after! That's what the big error dialog with the restart recommendation is for.

I was never really able to understand what was being asked for before. So basically you want to be able to state, "I want the final image to be 300 x 220 pixels." and to then crop out any area that has an aspect ratio of 300x220 (in other words, after simplifying the fraction, that's 15x11), and to have it then resized to precisely 300x220 pixels.

First, PLEASE STOP SHOUTING. Second, please read the rules. Thread Closed

I'm not sure what you're looking for here. This is not a C# developer forum. Thread Closed

First, create the logo image at the highest resolution you can deal with. Now, this first assumes that you have read up on what exactly "resolution" means: viewtopic.php?f=34&t=32569 . For instance, changing the "Resolution" from 96 DPI to 300 DPI does not change the fidelity of the image as it appears on the screen. It only affects the default physical size used for printing. For instance, the Paint.NET icon (the clouds + mountains + paintbrush) was authored at a pixel size of 2048 x 2048. It is then feasible for me to reduce it to pixel sizes of 256x, 48x, 32, and 16x, which are all the standard Windows icon sizes. If someone asks me for a "print version", that usually means they want 300 dpi. So I set the image to "300 dpi", and send it to them. In reality, the only thing that happens when I set it to "300 dpi" is that the number 300 gets written into the file instead of, say, 72 or 96. The pixels do not change, and the image has not actually "grown" or "shrunk". It is only a hint for your desktop publishing or word processing software with respect to how large you intend it to appear when printed on physical paper. Also, you should always use .PDN or .PNG. If you use .JPG or .GIF, they will mangle the quality of your work. Those file formats are intended to be used for photographs and low-bandwidth web images, respectively. Not logos.

I'm not sure what you mean by this. Got a crash log for me? (pdncrash.log, on the desktop)

Yeah, well ...

I would love to fix it, but I've never ever been able to reproduce this in the 6 years that Paint.NET has been around.

Umm ... ok? We aren't psychic. You're going to need to provide a lot more detail than just "I'm having problems"!

First, Simon Brown is correct in that you must be running the latest version of Paint.NET, which is v3.5.3. Second, I don't see the point to your "test" at all. You're using Paint.NET, which is a raster graphics editor, and round-tripping some text through several quality-destroying file formats. You then compare it to Word 2007 which is a word processor and which stores its data in a manner that retains all semantic meaning related to text. When you compare printing pixels vs. printing text, the latter will always win. When you copy from Paint.NET and paste into Word, you are pasting a bitmap. Word does not and cannot reify the text out of that. Especially when you've done the weirdest thing I've ever seen anyone do, which is to save in .GIF then .JPG then .PNG (what on Earth are you doing!?). If you want to print crisp text, then just use Word!

Sorry, but there is no support for anything related to Linux and Paint.NET. Thread Closed

Then try HsvColorF (new for 3.5.2).

This update fixes a few small bugs. As usual there are two ways to get it: 1. Download directly from the website, http://www.getpaint.net/ . There is no need to uninstall the old version; that will be taken care of automatically. 2. Preferred: Use the built-in updater from within Paint.NET. You can go to Utilities->Check for Updates, or you can wait for the following update dialog to show up automatically within the next week or so: Changes and fixes since v3.5.2: * Fixed DirectDraw Surface (.dds) file format support for CPUs which do not have SSE2 (Pentium III, Athlon XP) * Fixed an issue with the File->Save dialog related to file type plugins that were only written for opening (importing). * Fixed some crashes which were supposed to be "out of memory" errors. * Fixed a race condition with the New Image, Canvas Size, and Resize dialogs. If you typed extremely fast you could cause a crash by typing a negative number and immediately pressing OK or Enter. * Fixed a File->Save dialog issue in Win7/Vista where it could ask you about overwriting the wrong file.

Closing this thread. v3.5.3 is now available.

Good catch, fixed.

Run PdnRepair.exe in C:\Program Files\Paint.NET.

This is just the behavior of the File->Save dialog that Windows ships with. Learn keyboard shortcuts: Alt+N jumps to that text box.

Actually I found the crash log. They are actually overflow exceptions coming from GDI+; they are not stack overflow exceptions (easy enough to confuse them though). From looking at the crash log I have two recommendations: 1. Install XP SP3. The log indicates you are still on SP2. Service Packs are very important to keep up-to-date with. 2. It looks like you have a Lenovo hotkey application hook installed, and the floating point exception masking is being futzed with (on the "Processor:" line, it says fps=0x11, but it should say fps=0x1). Try disabling/uninstalling it, if possible. The DLL listed in the crash log is C:\Program Files\Lenovo\HOTKEY\hkvolkey.dll . These types of programs have been known to cause exactly the issue you are seeing. It also appears there are hooks running from the following, which you should also investigate if disabling Lenovo app doesn't fix things: 1. Something called "Dropbox" 2. Something called "TeraCopy" 3. Adobe Acrobat has a PDF hook (probably open/save dialog related) 4. There's some ATI dll 5. Something called Hummingbird Neighborhood 6. Symantec Endpoint Protection These are just from looking at the list of "Native Modules" in the crash log, which indicates what DLL's have been pulled into the PaintDotNet.exe process.

Please attach the crash log here too, thanks

I don't know why everyone assumes I'm not adding their pet features because they're "difficult" or something. I've never stated or implied anything like that.

Please, go read the rules. We also don't much care for the whole "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" thing :? Not trying to nitpick, just trying to be fair to everyone else who's already read and following the rules.

PLEASE STOP SHOUTING and edit your thread title first! :shock:

It's not lying to you, honest.