Rick Brewster

We're releasing this to fix a few of the bugs we've found since v2.61's release. This is not an alpha, beta, or release candidate, and as such does not expire. Get it via the built-in updater (File -> Updates -> Check Now), or on our website ( http://www.eecs.wsu.edu/paint.net ). Changes: * Small icon (16x16) is brand new, redesigned so that it is clearer * Application resolution is no longer virtualized in high-DPI mode in Windows Vista * Fixed race-condition related crash with Edit->Paste and Move Selected Pixels tool ("Object is in use elsewhere") * Fixed some font related crashes that occur when standard fonts are corrupt or missing * Fixed a crash that sometimes occurs when trying to save files whose name begins with a period * Fixed a rare division-by-zero crash in the Clone Stamp * Fixed rare crash related to scanning * Mitigated rare crash that can happen in various places, ("GetRegionData returned false, GetLastError() = 6") * Improved crash log reporting Here's the post that announced v2.6: http://paintdotnet.12.forumer.com/viewtopic.php?t=994 , and the one that announced v2.61: http://paintdotnet.12.forumer.com/viewtopic.php?t=1187 Anyway, that's all for now!

There's probably 2 or 3 other threads on this very same request, I think you can probably find it with a search.

Sorry, but this has been discussed at length before in several other threads. This will never be implemented in Paint.NET.

Don't worry, it's on the charts for our next release.

Thanks, glad you like it! And of course, feel free to ask questions and post suggestions.

My stand on this is ... do whatever you want, as long as it rocks If KayCee is fine animated banners for the contest, then I don't see why not.

Moved to General Discussion No, we will not be implementing this, nor do we have a currently plugin framework that would enable this.

Moved to General Discussion because it's a general question, not tutorial-related Sorry, we don't have tutorials in PDF form. All the tutorials are on this forum.

So you want CodeLab (see the Plugins section of our forum), except that it should use HLSL or something similar.

This isn't usual "pictorium" fare, but there's a new 16x16 version of the Paint.NET icon that will debut in our v2.62 release Vista icon guidelines call for the 16x16 icon to be "front facing" and I couldn't agree more, so instead of having a blindly down-sampled 16x16 icon, I made a new one this afternoon with Paint.NET, then merged it into our ICO file with Axialis IconWorkshop 6.01. 32x32, 48x48, 64x64, and 128x128 versions remain unchanged. Some screenshots of it in action: Paint.NET Main Window (and Help->About) About dialog Task bar Start menu Setup Wizard

Paint.NET currently doesn't expose a plugin framework for something like this. Key word being currently.

So how's the contest going? Any banners to show off yet?

Originally posted here: http://blogs.msdn.com/rickbrew/archive/ ... 92633.aspx Like the title says, Paint.NET has been downloaded over 2 million times now. Thanks to everyone! This nerdy little application that was originally just a senior design project has really grown way past anybody's expectations. In March our website did just a hair under 1 terabyte of traffic, and that was with BetaNews handling almost all of our actual downloads. In other news, there will be a v2.62 release shortly. Like all v2.6x releases, this is a bugfix release. There will be no new features, and no documentation changes. Just to define things, our v2.6 release is in what's called maintenance mode. We're still working on v3.0, but since it's going to take awhile, we are also fixing bugs in v2.6 as appropriate. This way important bugs get fixed within a few weeks instead of, well ... read the next paragraph. And as for the next major release ... ok, I'll talk about it a little. It will be version 3.0 (hardly a surprise), with its major features being MDI, layer masks, layer adjustments (and adjustment layers, the difference of which is interesting but important), and whatever other stuff I can't remember right now. It will take advantage of Vista, but will not require it. As always, the goal is to add functionality and features without increasing the UI's complexity. It's practically a rewrite of Paint.NET, so I don't expect to see it be available for quite some time. Maybe for Christmas? We will see. Anyway, thanks again to everyone who uses, recommends, mirrors, distributes, blogs about, and laughs at Paint.NET. And thanks to everyone who's been sending in those pdncrash.log files -- we really are using them to find and squash bugs! There is one bug in particular that is interesting enough that I may just blog about it soon. So if you see the pdncrash file on your desktop, please e-mail it to us.

Sorry, there's no "fullscreen" mode, nor can you turn off the toolbars or set the default canvas size. We've really designed this app for 1024x768 and larger screen sizes. But if you could describe in detail how you're using Paint.NET, and what you're using it for (for example, aatwo, another forum member, draws cartoons), that feedback will be useful for us going forward.

You're not making this any less vague. "I want one image to cover all the layers" ... I'm guessing what you want to do is to save as a JPEG or as a PNG, so that users can view the image without having to have Paint.NET. If so, just go to File -> Save As and save it as a PNG or JPG. It will be flattened for you. Or you can just use the Image -> Flatten menu command. Otherwise I have no idea what you're talking about.

What will make the images not look crappy is not using GIF in the first place. If you don't want to deal with layers in Paint.NET, simply don't use them.

I don't understand your question. You want one image to contain all the layers? You must use the PDN image type for this. All other image types must first flatten the image before saving. Or do you want to export each layer to its own image file?

Wow, good find! I'm waching the "installation" tutorials where he actually starts out with no prior knowledge of Paint.NET. Definitely highlights some ways I can make it easier

Please read our FAQ. http://paintdotnet.12.forumer.com/viewtopic.php?t=489

Paint.NET's architecture is such that it must: 1) Hold the entire image in memory 2) Have a bitmap used for compositing the image 3) Have a scratch surface (3) is not always in use, but it's important to have it allocated because it makes error handling much simpler. If you clicked on the Clone Stamp and suddenly got an out of memory error, that would be lame. (2) is not always important, as a single layer image effectively needs no compositing. So, to compute the memory requirements for an image, the following formula can be used: (W x H x 4) x (L + 2) W is the width of the image in pixels, H is the height in pixels, 4 is because each pixel takes 4 bytes, L is the number of layers, and the +2 accounts for (2) and (3) above. So for your 7680x2880 image, which I assume has 1 layer, the total memory required is: (7680 x 2880 x 4) x (1 + 2) = (88473600) x (3) = 265,420,800 = 253.125 MB RAM When you resize an image, you must have enough memory to hold the image at both its old and new sizes. Other factors influence how much memory is available. For instance, just because there is still 1 GB of virtual address space available does not mean that there is 1 GB available contiguously. Programs like Photoshop and The GIMP have complicated memory managers that tile the image, swapping it out to scratch pads (disk) as necessary. This impacts coding complexity because every part of the application that works with the image must take the tiling in to consideration. It also affects performance, but has the advantage of being able to work with much larger images. For Paint.NET, I purposely chose a design that enabled coding simplicity for many reasons. If you have a 64-bit CPU and OS, you will have a much harder time running out of memory. You may also look into the /3GB switch for the boot.ini file, although I do not know for sure that this will help: http://support.microsoft.com/default.as ... E05B0ABAAA

It's not about physical memory. On a 32-bit OS there simply isn't enough virtual addressing space to fit really large images with Paint.NET's architecture.

Sounds like there isn't enough memory then.

Nope and no.

This file is not available for download anymore. Version 2.5 has been completely discontinued.

Moved to Bugs & Troubleshooting A few questions: What is the size of the image, in pixels? You can view the properties in an explorer window. Second, please post the contents of the pdncrash.log text file, it should be on your desktop.