Rick Brewster

Dang, I must be getting sloppy or something. I updated the description, the download URL's, but I neglected to change the version number. So 2464 still thought it was the latest version. 2461 would have updated successfully though Fixed for real this time, I swear!

Ok I found and fixed it, was simple enough. It'll be working right in the next build!

Yeah it's been that way since 2.6 actually! I'll fix it don't worry Shouldn't be any more of a problem than with the Effects menu, I'd imagine.

Like it says at the top of the Tutorials forum, it is reserved for tutorial publishing ONLY. Moved to General Discussion

This has been requested before, a lot. Use the search facility. This is essentially a duplicate post. Locked

woops fixed :oops:

Yup, it sure does. I"ve filed a bug, thanks.

Yeah I just moved it over in 2464. It's kind of a primary set of features, so it makes sense to put it front and center rather than hiding it away.

It's probably the same as the Auto-Levels crash. I marked a few methods in ColorBgra as obsolete. But then in FromBgr() I accidentally changed it from calling FromRgb to FromBgr ... itself! So, infinite recursion loop causes major death. Fix will be out soon, I just got done installing a build of Vista so I can do that now.

It's already in there for 3.0. And FYI, the correct term is not antialiasing -- it's actually the resampling algorithm. Right now it always uses bilinear, and what you want is point sampling, aka "nearest neighbor."

In general it results in pictures that have a very poor and worse than amateur quality look to then. If this is ever possible in Paint.NET it will just be part of a more generalized brush system.

Right but at that time they are no longer "effects" and are now a more generalized image/document processing mechanism. By design the effects system heavily restricts the type of information that an effect has access to. What you are talking about is more of a full blown scripting system that has full access to the Paint.NET document and object model.

This was done on purpose. The spray paint tool is junk, so it was left out.

Try a photomanipulation. http://browse.deviantart.com/digitalart/photomanip/ ^ Browse around for some ideas!

The Pan tool was removed in v2.5 because it was redundant with the added ability to hold space and drag the mouse around. Also because the Tools window was taking up too much space. In 3.0 we have extra space to use because the UI has been shuffled a little bit, and I'm adding a gradient tool. Some people just like having the pan tool, it's something they're used to.

Are you just checking for pixels with an alpha value of 255? I would suggest, instead, rendering the drop shadow for all pixels and then blending that based on the source texel's alpha value. You can use UserPixelOps.Normal.ApplyStatic() to do this on a per-pixel basis. Paint.NET 3.0 will have some blending utility functions that make this sort of stuff (taking the alpha channel in to account) easier.

How's this? It limits its height so that it only goes as far as the bottom of the screen (excluding the taskbar). But it will always show a minimum of 3 items (unless there are less than 3 items of course), so if you move the window near the bottom of the screen the list end up being above the dropdown arrow button. (click for full-size)

Paint.NET doesn't run reliably with 128 MB RAM anyway. I'd suggest upgrading to a minimum of 512 MB for all computing purposes.

Renamed post title Please don't use generic thread titles like "Question." It makes the forum impossible to navigate.

Pretty sweet lookin'.

Another quick sneak peak at 3.0. This feature is addressing two major issues that I receive enough e-mail about to cause me to do this: 1) People ask to be able to change the tool that is active at startup. Many people are used to having a selection tool active for whatever reason. 2) I get a lot of e-mail from people asking why the magic wand and/or paint bucket tools are "broken". Either it fills/selects everything, or nothing. The reason is that they have accidentally set their Tolerance to 0% or 100%, and this setting is remembered when you quit (it is "sticky"). Also, many people accidentally click the alpha blending and/or antialiasing buttons and ask why there is such terrible quality drawing. So, to address (1), you can choose what the startup tool is now. To address (2), none of the toolbar settings are "sticky." However you can now specify what their defaults should be:

Yeah I haven't fixed the "takes over the screen" issue yet.

Nevermind, I published the update manifest wrong. Should be fine now!

Just to double check, but if you click on Check for Updates and then the Options button, that both checkboxes are enabled? Specifically, "Also check for pre-release (beta) versions" ?

I'm not planning to make changes to the Line/Curve tool for 3.0. But that is where it would go, sure.