Rick Brewster

Yup, this is a known issue. We'll have it fixed for the next update.

You downloaded the source code. You want just the installer -- it's under 5mb. Here's a direct link: http://www.eecs.wsu.edu/paint.net/files ... t_2_1b.msi I highly recommend downloading the v2.2 Alpha 2, however. It has some really great new features and will even tell you when newer versions are available: http://www.eecs.wsu.edu/paint.net/files ... Alpha2.exe

... and hopefully we'll be upgrading them in time for the v2.2, I should add.

Then that's a different issue, and is one we're aware of. Our text editing facilities are currently quite rudimentary and we are planning to upgrade them.

It depends on the font you're using, Sidney, nothing else.

Paint.NET doesn't read or write PSD files, sorry.

Install v2.2 Alpha 1. There is a "Clear this list" command in there.

Yes, it's yet another reason we need to revamp the docs for v2.2 I've taken this into account for our schedule.

vtt395, I don't understand what you mean by "don't use antialiasing, it's kind of weird!"

"Determining which color is transparent" -- we use an alpha channel, which gives variable transparency (256 shades of transparency, so to speak). The original Paint has polluted the imaging world with this notion that "one color" is transparent. That's not how things are supposed to work. As for filling with transparency, check out the latest v2.2 Alpha download. There is an option called "alpha blending" which you can disable, and then you may fill a region directly with the alpha value you have selected in the Colors box. Otherwise if you select an alpha value of 0 and use the paint bucket it says "oh, this color should not contribute anything, so I'll leave the pixels alone."

I have no idea what you mean ... what difference between resizing and scaling do you mean?

Only 85 forum members, but over 600,000 downloads ... I think we're doing ok

You didn't say where you're copying the special characters from, so I don't know what to tell you. It generally depends on which font(s) you're using, because we support the full Unicode range of text characters. I've seen people use Paint.NET to put Japanes and Arabic text on to images, two languages that are completely alien in input methods compared to English. I just tried pasting your 'â' from this forum post and it showed up perfectly in Paint.NET.

Ctrl+V works when you have the text tool selected and have set an insertion point (i.e. you have the blinking cursor). I'm afraid you're misunderstanding how Paint.NET and Windows work. There's no facility built in to Windows that provides a rich text editor, especially not in the way that we require one (right smack in the middle of a bitmap). The text editing that Paint.NET currently has was written completely from scratch by Chris Trevino a year and a half ago. It is limited in functionality because of the time constraints we had. To upgrade it to include everything you're asking for is something I have been planning to do for awhile but is also something that will require significant time to do (probably several weeks).

No, we don't have sample code for what you're trying to do. Paint.NET was never engineered to work on a web page, it doesn't work like that at all. PaintDotNet.Data.dll has code for reading and writing data, and for rendering it to the screen in the context of WinForms, not WebForms.

Nope, sorry, We don't have 2 months to engineer it from the ground up. XP provides a DLL that implements it all for us with only 1 page of code, most of which is error handling.

Use Printscreen to copy the whole screen, or Alt+Printscreen for just the current window. (this is built-in Windows functionality). Then in Paint.NET: File -> Acquire -> From Clipboard

Try these out, http://www.codeproject.com http://www.gotdotnet.com

Visual Studio 2005 contains a set of "new style" (Office 2003 style) icons that are freely usable, and we plan to make use of those when we move in that direction (after v2.2). Things like Open, Save, and Print icons will be upgradable pretty easily because of this. However, many of our icons were created by us and will be harder to upgrade. I'm afraid we're not artists. The reason we don't have super awesome icons right now is that it'd be an enormous undertaking to upgrade them all from "16 colors" to 256- or more colors. By my count we currently have 112 icons for v2.2.

The current plan is to release Paint.NET v2.2 using .NET Framework v1.1 and to then do a (hopefully) quick feature-parity port to .NET Framework v2.0. This will mostly be done so that we can have a 64-bit "native" version of Paint.NET. After that, the plan is to migrate the UI to use the enhancements added in .NET 2.0. This "version 3.0" of Paint.NET should be available sometime in 2006, and should have numerous other feature additions and enhancements.

1. You have permission to do whatever you want with the source code! The license that we use, the MIT license (http://www.opensource.org/licenses/mit-license.php) can best be summarized as "do whatever you want, just don't remove our copyright." 2. DotNetWidgets has been succeeded by SandBar, http://www.divil.co.uk/net/ , which looks very similar to the toolbar and menu enhancements present in .NET 2.0 (Whidbey aka Visual Studio 2005). The author seems to have completely deprecated and discontinued DotNetWidgets. We will be migrating to the .NET 2.0 enhanced toolbars and menus in the future. 2 weeks doesn't sound like nearly enough time, but good luck!

Our text editing is fairly primitive right now. We're looking to improve that soon. Pasting via Ctrl+V should work, however.

This has been fixed for our next release.

Version 2.2 supports GIF transparency. You can download the Alpha 1 from our download page: http://www.eecs.wsu.edu/paint.net/download.htm ... I've wanted to say that for so long (we didn't support GIF transparency for a looooong time and people have always asked for it)

Which version did you try?