Rick Brewster

Umm, there is no paint shop pro plugin.

Sorry, this won't be happening. And it is not possible with a plugin.

This is not possible with the current plugin system. And yes this has been asked before. Locked

This is not an appropriate place for that kind of bickering, trickman. Locked

I'm sure the applications you have that don't work in SP2 have been updated by now so that they do work. It's been two years. The system requirements for Paint.NET will not be lowered to allow XP SP1. I believe I've already stated this several times, and this decision will not be changed.

Functionality changes? It's Windows XP, it functions just like it always has.

And what are you basing this statement from ... ? Just install SP2. It's over two years old now, it's free, and has numerous regular and security improvements. Like I said before, trust me when I say that I know what I'm doing when it comes to setting system requirements. I honestly do not understand anyone's trepidation about installing it. Paint.NET's system requirements will not be lowered. If you do not install SP2, then you may not install Paint.NET.

Just install SP2. Problem solved. Trust me when I say that I know what I'm doing when it comes to this stuff. SP2 has been out for over 2 years and is a free upgrade.

Hmm,looks like the same crash BoltBait had here, http://paintdotnet.12.forumer.com/viewtopic.php?t=2275 That ThreadBackgroundMode has been a real pain with respect to this

As is clearly stated at the top of the Tutorials section, that area is reserved for tutorial publishing only. Moved to General Discussion

Not gonna happen. I am not rewriting the Open dialog, nor am I going to hook into the one that Windows provides to add this type of functionality. The best idea is to just upgrade to Vista: there you get very nice, huge 256x256 thumbnails if you want them. It looks awesome. Paint.NET 3.0 has been upgraded so that .PDN files have larger thumbnails embedded in them in order to take advantage of this. * Oh and you can have these 256x256 icons in all applications that use the standard Windows-supplied open/save dialog.

If you're referring to any animated GIF programs that I’ve written, I wrote my GIF codec from scratch in late 2003, after the LZW patent expired in the U.S. Other than the link provided, all sources I saw at the time listed only the Unisys patent (where'd this IBM B.S. come from?), and the Unisys one was expired in June 2003. As far as I'm concerned, my programs are legal and have been... I believe Evan is correct. IANAL though.

Stop asking to add options and preferences. I already said no.

DNS was configured wrong, it was off by 1. Should be up again within an hour or so.

Yes ... new hosting ... trying to figure it out.

I posted some more commentary about the v3.0 release to my blog, http://blogs.msdn.com/rickbrew/archive/ ... ntary.aspx with a screenshot

The Forms Designer in Visual Studio will not load most of our forms or controls because of the way we handle resource loading.

Moved to General Coding / Development

So you basically want to change the center point that the zoom blur operates from. ... stay tuned. (but not for 3.0)

You can crop it after you paste it. Paint.NET is not a screen capture tool though -- the work to enable a feature like that just is not worth it when the built-in facilities Windows provides, along with simple selection + cropping, are complete and simple to use anyway.

Why would you need to do that though? Seriously -- processing left->right, top->bottom takes most advantage of cache locality. Anytime you access a pixel in memory, the incurred cache miss will bring in the surrounding pixels as well. But 'surrounding' is based on the memory layout, and in our case that means horizontally. So having left->right as the inner loop exploits this. When you reverse the loops, you nullify your cache. So let's say you start at (0,0) and run all the way to (0,1023). Every one of those memory accesses has brought in pixels (0,n) through (31,n) [for instance]. By the time you get to the bottom, just going based on a simple LRU cache ejection algorithm, you're already kicking out the top rows' cachelines. So when you start your next loop at (0,1) you're back to cache misses. Which means you're doing 8 to 32x the memory bandwidth, depending on the cacheline size of your processor. But if you access (0,0) and then (0,1) right away, you do a cache miss and then a cache hit: much faster.

No, sorry.

Well you have to go click checkboxes or delete buttons somewhere anyway.

The goal is actually to remove interstitial dialogs like that, especially when they are redundant. Why ask the user what layers they want to import when they can just go and delete the layers they don't want using the normal Layers window UI anyway? It's a win-win: the user isn't bombarded with tons of dialogs during the import process, and I have less code and UI and dependencies to maintain. So, this was removed on purpose.

Yeah, I don't get it. How is it funny that you're using the Paint.NET icon for your avatar in another forum? Doesn't really make sense.