Rick Brewster

The history was never designed to be persistable. Plus, if we were to save the history with the PDN file, we wouldn't be able to change how things work in the future. This would prevent us from adding, removing, or changing things (or fixing things!). For example, if we wanted to rewrite the line drawing tool, it would probably need to store different data in its history action. But our hands would be tied, because the format was already set in stone. We could write code to migrate the history data between different schema versions, but that just doesn't scale with 2 developers and tens of history action types. We'd spend all of our time figuring out data migration issues instead of adding, changing, or fixing things. Which leads to the next problem. Maybe we'd just discard the history when we did change things, but that would also be obnoxious (I can imagine the e-mails now ... "I upgraded PDN and my history disappeared!!! BUG!"). Of course you may point out that we do persist history data to a temp directory while Paint.NET is running. It looks like every history action results in 1 file in that directory. This is partially true, but also misleading: not all history actions save their data to disk. And those that do only save the "big" portions of their data (e.g., large bitmap regions). And even then, they are still coupled to the rest of the history action that resides in memory. We do this to relieve memory pressure, as otherwise you could run out very quickly. Just try using Paint.NET v2.0 for awhile and you'll see the memory usage keeps going up and up and up. And yeah, it would result in huge files. Or we'd save two files, a .pdn and a .pdn_hist or something, and there'd be the possibility of mismatches between the two. It would just be a huge nightmare. So, in summary, not saving the history is the lesser of all evils or nightmares. Sorry guys. I of course agree that it would be Very Cool.

That's a plugin for Windows Cleaner, not Paint.NET.

Reno, comments on the zip file: * What is the point of the "fr" and "Logiciels" directories? The former is empty, and the latter contains no files, but many nested subdirectories. * In the Files.AboutCredits.rtf, please remove DotNetWidgets and Skybound VisualStyles from the list at the very bottom. * Please don't translate the MIT License unless you've found an actual, authentic translation somewhere (did you? I'd be very interested to know where!). This is for very important legal reasons. * In File.html, looks like the image for the Save Configuration is vertically stretched a little. Probably just an errant "width=" or "height=" tag. Other than that, it looks really good.

Sheesh! So it was! fixed! :oops:

Oh, I wasn't trying to reprimand you, don't get that impression. I'm just trying to make sure that we not set a precedent by leaning on Softpedia's claim in order to verify that Paint.NET is indeed spyware free. (although, in this case they are correct: Paint.NET is not spyware, nor does it come bundled with any)

Well, Softpedia is correct in this case, but please let's not use them as a (anti-)spyware authority or reference.

The ad banner helps out forumer.com, but does nothing directly for Paint.NET. ... fyi They host the forum free of charge.

Yeah, don't worry about the big red bold text if you're just trying to download and install for personal use.

Thanks, glad you like it!

There has never been an "Attributes" item in the Image menu, so I'm not sure what you're talking about.

Let me reiterate: Paint.NET does not connect to the Internet if you disable the update checking. The signature verification is being done by other software or configuration settings on your system and is not something we enable. Please read the post that I linked to above for more details. This verification is done in-process and is thus attributed to Paint.NET by your firewall software. I don't know how I can make this any clearer.

Nope, sorry. Right now it isn't possible due to our plugin architecture (which we will fix for a future release), and because of the reasons detailed here: http://paintdotnet.12.forumer.com/viewt ... =photoshop

Well I have Oblivion now, finally. It definitely demands a high-end system ... :shock:

Right, like I said, focus games. If we don't focus the Tools window when you move the mouse over to it, we don't get the tooltips. Part of this madness is due to the fact that Paint.NET is composed of 5 windows (4 "floaters" + 1 main window), which is not standard. The insanity thus ensues trying to make it behave like it's 1 logical window.

The update checker is something you can easily opt-out of during setup, or while the program is running. And like I said, those other connections you are seeing are not Paint.NET. We sign the actual EXE's and DLL's that get installed to Program Files. Most applications just sign their setup packages that you download from their website.

We already do a lot of that. It's just a cat-and-mouse game where you have to find all the situations where focus and input have to be redirected from one part of the app to another part. It can be hard to do without turning the code into spaghetti mess.

Scroll wheel in the layer window isn't something I can promise. We have to play a lot of "where's the focus?" games to make all of the windows appear as "one" application. If you used Paint.NET v2.1 you will remember that the floating windows' title bars would flick between focused/unfocused whenever you clicked on them (bleh!). 2.5 fixed that by doing some tricks to prevent them from ever drawing in the "inactive" state.

It seems as though all you want to do is pick a fight here. You won't find one. If you continue to post in this fashion you will be banned from this forum. Paint.NET is a free application that is continually evolving. If you don't like it, then don't use it. This thread is dead.

George, I'm afraid you have missed the point completely.

This has been fixed for our v2.61 release, scheduled for the end of this month.

I've found and fixed the bug (it'll be there for v2.61). We store the location of the shortcut in the registry in HKLM \ Software \ Paint.NET \ ProgramsShortcut. When we go to delete it, we do some sanity checking on the filename there: does it end in .lnk, and is it in the right directory? Turns out the code for the latter was flawed and was returning false negatives (I guess I'd rather have that than false positive and have it delete some other file).

Nah, I don't even have an XBOX 360 yet, nor have I been able to find a copy of Oblivion for PC (I know, I know, I should have pre-ordered...).

Ack. I'm seeing this as well. This used to work. I'll make sure this is fixed for v2.61, which we're planning for the end of the month.

The method I listed also lets you keep the coloring separate from the image. Easy to erase the stuff you've done, redo it, etc.

Another good way is to: 1) Make the layer black and white (Layer -> Adjustments -> Black & White). This actually desaturates the image, but we give it a simpler name. 2) Create a new layer (Layers -> Add New Layer) 3) Set this layer's blend mode to Multiply (Layer -> Properties) 4) Now color on the layer using the Paintbrush tool! (This probably works better than using the Recolor tool)