Rick Brewster

The problem with Save is that it is a modal operation. To put this in terms that are relevant to the end-user (that's you!), this means that while a save operation is in progress, you cannot do anything else. At all. I can't let you change the image while I'm saving it. No ifs, ands, or buts. So let's say it takes 10 seconds to save your image, which is not too far fetched on a middle-of-the-road system working with a multiple layer 1024x768 or even 640x480 image. If I have an autosave feature that fires every 5 minutes, it gets very annoying to have it pop up while you're in the middle of drawing so it can save (even if the "pop up" is just the mouse cursor changing to the hourglass). Or, of course, you make it more intelligent so that it waits until you aren't in the middle of doing something -- even then, it doesn't prevent you from deciding to do something in the middle of it saving, and you have to sit and wait and wait for it to finish. Compare this to when you invoke the Save command yourself: you are also preparing yourself to wait for it to complete. You think, "Ok I'm going to save my image. I know it might take a few seconds, so while it's saving I'll amuse myself with the super awesome progress bar animation. Or maybe I'll think about puppies. They are cute. Oh cool, it is done." You haven't made those types of short-term preparations with an automatically invoked save operation. Now, this is actually partially an artifact of the way the data layer in Paint.NET currently works. There is a lot of work I want to do on the data layer for a future version that would incidentally enable me to do a save operation while still allowing you to continue editing the image. But remember, when I say "a lot of work", that also means "a very long time from now." There's also error handling. Some of the codecs require large amounts of memory allocation to do their job, and this is a very error prone operation ("no more memory? you = crash!"). It's just not cool if you're using Paint.NET and then 5 minutes later it decides to save and then crash ... and you didn't even touch it! If it crashed halfway through a disk write operation, your image is now hosed. This can of course be mitigated in several ways (e.g., save to a temp file first, then swap the temp and real files ... suppress errors during auto-save operations ... etc) but it is still an obstacle. I'm going to go ahead and put this in the Popular Feature Requests thread.

There are already timer programs out there that you can set up to do this. I don't see value in Paint.NET implementing this type of "babysitter" feature. You can also just get into the habit of pressing Ctrl+S (Save) every once in awhile. I end up hitting Ctrl+S all the time when editing documents, and programs like OneNote leave me a little uncomfortable sometimes because they don't have a Save command. (I like OneNote though -- I've acclimated to that difference)

"Sharpen" does not mean "un-blur" -- the two are not inverse operations of each other. I think that's where there's some confusion.

You should also consider installing the 64-bit version of Vista (I noticed you're using the 32-bit version). That will help Paint.NET a lot.

Nope, nothing of that nature. I'd never let it happen. I've had people approach me suggesting that I bundle things like toolbars and other dubious software because they can generate money (like $1 per installation, or 5 cents per 100 search clicks or something). I told them to drop dead.

I can't understand the question at all.

Yeah use of capitals is a little more acceptable when saying "thanks" and when not used as the thread title. When somebody says "THANKS!" you don't reply with "turn off your caps lock", you say "you're welcome!"

Nope, no harm

Nope, no plans to add this feature.

PaintDotNet.exe, which contains MainForm, is not a class library. It's not designed to be used that way at all. It's meant to be an application -- not a component.

Umm ... what the heck is U3? But no, we won't be providing any alternative installers or versions. This doesn't prevent you from doing it yourself though.

Err, don't forget to send in the crash log.

But where is the BMW?! ... Oh that's right. It already won the race.

It's not done yet. Why would it say Finish? The behavior you are seeing is correct.

This is just a minor update that fixes a few small bugs that have been found since 3.0's release. Get it the usual way: either via the built-in updater (Help->Check for Updates), or from the website at http://www.getpaint.net/ Changes: * Fixed: Crash when trying to save a palette with a blank name * Fixed: Changing an image's DPI resolution did not set its "dirty" flag (you would not be asked to save changes) * Fixed: Error messages at startup were covered by the splash screen * Fixed: Crash when a modal dialog was open (such as an effect) when the user tried to logoff/restart/shutdown Windows, and they chose to save their images * Mitigated some CPU usage issues when the app was minimized and a complex selection was active

skatterbrain, What you're asking for is definitely not "fairly basic" from my side of the fence (that is, as the developer). Paint.NET has reached a point in its development where it needs a significant overhault to enable any of the features you are asking for. Because I'm not working on Paint.NET full time, I simply can't give an estimate for when any of these features will be available. It could easily be years and years, and my roadmap doesn't plan out that far ahead.

You could press F4

iba, your 2nd attempt doesn't make any more sense than the first one.

I think your math is off. If you draw from 100,100 through 105,105 then on each axis you have 100, 101, 102, 103, 104, 105: that's 6 pixels.

Sorry, no. Paint.NET does not support Photoshop plugins.

GangstaCrab, your avatar image is too wide. Please fix it.

Who said anything about being angry? The text in quotes is meant as a bit of facetiousness. I gave you a realistic assessment of the situation. You have no idea what the code is like, so saying that it needs a "re-design" is a bit misplaced on your part. Please don't tell me what the code needs. That'd be like if you took an elevator ride in a skyscraper, it took "too long," and you suddenly jumped to the conclusion that the whole building needed to be demolished and then rebuilt to fix the problem. Anyway this thread is just circling the drain. It's obvious that some people have no desire to actually understand why I'm not spending all my time working on their requirements, and more interested in complaining about it. I see no reason to leave it open. Thread closed

Wow V.A. you're already off to a horrible start on this forum.

Please read the rules: this is covered in the FAQ. A quick search would have shown this. Thread Closed

10633 x 7421 will use up 78,907,493 bytes per layer. So take the number of layers, add 2 (one each for scratch and composition surfaces), multiply by that 78mb, and that's a rough memory usage number to start at. Paint.NET only works with 32-bit pixels, so the fact that your source image is 24-bit isn't a factor -- the alpha channel is still created, but filled in with all 255 values (all opaque). Having enough "space" doesn't mean there you have enough contiguous space in the virtual address space of the process. Task Manager presents an extremely simplified view of memory usage in the system. The real solution for you is to upgrade to a 64-bit version of Windows, where Paint.NET will be able to really stretch out and not give out of memory errors. Or use Photoshop, I guess.