Rick Brewster

Well I never promised anything. I said I had a prototype.

That PNG file is messed up. The alpha didn't carry over correctly. Just download the source code and find PaintDotNet.ico. I don't know why you need to go extracting and hunting for things...

The other issue is that Paint.NET needs the ability for a file format plugin to provide a load-time UI. This UI could be for configuration (esp. important for RAW) or for warning (esp. important for HDPhoto's more-than-32 bits-per-pixel formats).

Yes, it's possible. I already have a prototype working. It's a pretty simple matter to use the WIC hooks that WPF provides. The hardest part is determining which subset of codec configuration properties to support.

I assume that what you want is akin to what Firefox and IE7 have implemented: by default, new tabs are used, but you're free to create a brand new instance as well. Right now that mostly isn't possible because MDI is a fresh feature for Paint.NET and I wanted fewer moving parts on a change of this magnitude. There are a few unsolved issues* with instance management that don't make this possible yet, aside from the lack of a File->New Window command. * By "unsolved issues" I do not mean bugs. It's more along the lines of purposefuly limited capability with respect to wanting to ship in January instead of March.

I'm guessing it's a single core/processor system (just playing the statistics here -- most people don't have brand new computers). If Paint.NET starts running away with high CPU usage, it will make the rest of the system unusable because you said you want Paint.NET to have priority. In my experience and opinion, there's really only two times to muck with the priorities: 1) You have something that uses a lot of CPU and you want it to run in the background, effectively only using spare CPU cycles that nobody else is using. An example would be if you are doing a large compression job and you want to keep going about doing some other stuff. Having a dual- or quad-core system is actually making this less of an issue. If I have some large compression job going on the side (e.g. I'm making a ZIP file of the Paint.NET CVS server so I can do a backup), and if I had a quad-core system ... then I've still got 3 cores leftover that can do stuff at full speed. 2) You have a real-time application (e.g., MP3 player) that seems to be misbehaving by way of skipping audio or something, and you notice weird CPU usage patterns surround it. Sometimes setting these to a higher priority can alleviate that. When the real-time app needs CPU time, then by golly it is going to get it. But by the nature of the application it isn't going to be using a constant amount of CPU time -- maybe 100ms every 2 seconds or something. The foreground application automatically receives a priority boost anyway. I can almost guarantee that the computer is going to do a better job of managing thread scheduling than you can.

Switching PaintDotNet.exe to high priority is probably a bad idea. Really, if you want great performance, here's the things you do or want: 1) Have lots of memory. 256MB is the minimum but you really want 1 or 2 GB if you're working with large images. Less memory means more hard drive use which is extremely slow. 2) Have a dual-core processor. Paint.NET is heavily optimized for multicore systems. 3) Use 64-bit Windows. More RAM and better performance.

I like this one a lot. It's simple, but elegant and tastefully done. On the constructive criticism side, there seems to be a 1 pixel gap between the "monoliths" and their reflection.

You can also use this page that I've set up to track some 'buzz': http://www.getpaint.net/buzz.html It just has a few public web controls, but they're on one page so you don't have to track them all down. If you can think of anything else worth adding, just let me know.

Another thing that helps: 5) .NET Framework itself may need to be repaired This is a different symptom than what is listed for (4) above, but the solution is the same. This is worth attempting as a troubleshooting step as well -- sometimes, for whatever reason, .NET itself becomes corrupt or damaged and a simple "Repair" often fixes things right up. You can do this from the Add/Remove Programs control panel in Windows XP, or the Programs and Features control panel in Windows Vista. Here are some other resources that can help in this case, and which may be worth trying as a matter of standard troubleshooting if nothing else seems to work: A ) What to do if other .NET Framework setup troubleshooting steps do not help, http://blogs.msdn.co...07/8108332.aspx B ) .NET Framework Cleanup Tool User's Guide (and link to the tool), http://blogs.msdn.co...28/8904493.aspx

Well, what kind of error are you getting? Have you tried repairing your installation of the .NET Framework?

Found this just the other day: a PdnBench result on every page. http://www.hardwarezone.com/microsite/i ... ials.shtml

It's impossible that Paint.NET could cause this. What you're describing can only be done via a kernel driver (which neither Paint.NET nor .NET install), or hardware failure. My bet is on the latter.

You'll need to write your own program to do this.

This is because you're completely misunderstanding how the Effect system in Paint.NET works. There's no such thing as a post-render loop: your Render method is the implementation of the inside of the rendering loop. Your Render() method is going to be called from many threads at once and many times in a row. On a typical system it will be called 200 times from 2 difrerent threads (100 times per thread). So you are opening these input files 200 times and dumping this stuff out to disk 200 times as well, as well as creating 200 processes. You're also violating the Effect contract by writing outside of the region of interest that is specified in the parameters. When I call your Render() method, you must only and I mean ONLY ever write to the pixels described by the roi array from startIndex through startIndex+length-1. The reason your Render method is called many times is because each time you are called upon to render only a small portion of the roi array (roi stands for region of interest btw). So to quickly summarize: it's slow because everything is completely wrong. Paint.NET is probably the worst possible harness for what you are trying to do.

Yes, this does happen and it seems to be a framework (.NET) bug. Things just seem to get a little confused when the mouse-down and mouse-up events for different buttons overlap each other in time.

Sorry man, like the rules state you gotta be using the latest version , which is v3.01. Otherwise we just can't help you out. Thread Closed P.S. The answer is no -- you must have multiple instances open in 2.72 to open multiple images.

This is answered in the FAQ. Please read the rules. Closed

Sorry, but: no, no, and no (to answer the three questions -- I'm not repeating for emphasis). This type of plugin is not possible.

Nope that's just outdated text. Paint.NET 3.0 absolutely requires Windows XP or newer. I ripped out all the gnarly Win2K support code many months ago, so Paint.NET 3.0 is definitely making calls to system functions that are only available on XP and newer.

I'm Eric. I go by Rick.

Thanks, glad you like it!

What Dan said. An MD5 hash isn't necessary -- the digital signature allows the same type of verification.

The point of having the same key is that you press it multiple times to get to the tool. For example, you press S three times to use the Ellipse select tool. This simplifies selecting tools of the same type: if you know exactly what tool you want, you're gonna have the key memorized no matter what. If you're still learning things, you can think "all the selection tools are S, so I will press that key until I get the one I want."

You just have to use your own creativity really. What you're asking is basically, "how do I make something awesome?" and the number of answers is essentially infinite. There is no "Make Something Awesome" plugin. You can't just push a button and have the computer be psychic and do everything for you (if only!).