Rick Brewster

It sounds like you're working with some old documentation, possible going off of Dennis' old article about writing plugins for Paint.NET v2.1. Things have changed since then. 1. You need to specify EffectDirectives.SinglThreaded as a parameter to the base Effect class constructor. 2. If you specify SingleThreaded, then these will be thread safe because your effect will only ever be executing on 1 thread at a time. Otherwise, you must not use them in your Render() method, as GDI+ will complain loudly. 3. You should be using the overload of Render that takes an array of Rectangles, a starting index, and a length. No Regions. 4. You shouldn't have to worry about "using" the threading model of Paint.NET. Everything is set up for you automatically. If you are having problems it's likely because you are incorrectly assuming things about the way Paint.NET is calling in to your Effect. The effect system is designed such that Paint.NET will call your Render() method to tell it to render a specific region of the output surface. You must NOT render anywhere else in the output surface.

Oh yes, I know about this. This is pure theft. Our license does not cover derivative works of this nature. He has not released this yet, so we have not yet taken action.

Edited to change "???" to a single question mark Those multiple !'s and ?'s really get obnoxious after awhile ...

A clickbable / interactive tutorial would be pretty sweet. But the whole app? Hmmm okay I'll dump PDN 3.0 dev work and spend the next two years building a web page. No, I don't think so ... no thanks (I guess it really would be Paint ".NET" in that case though, ha!) And I just don't believe it would be very useful anyway. "Wow I have a paint program ... but it's in a web browser. And it's really slow. Why is it using 100 MB of memory for a 800x600 picture? And most of the features I use aren't there. Where does this file get saved? Argh it takes 5 minutes to upload/open my 7 megapixel camera pictures. Goodness!" I think a web page image editor would be best focused on uploading an image, cropping/resizing, and sharing ("hey mom look at my picture ... just click on this http link"). And if I'm not mistaken you can already do that on some websites. Web page apps have their purpose -- just look at Hotmail or Gmail. They provide the functionality that many people need for casual to medium e-mail use. The omnipresence is also nice, as you can access your e-mail from almost anywhere. For professional use though, something like Outlook w/ Exchange Server is much better, for many reasons.

No they don't have their own copy of the Tolerance setting. That would be very confusing or frustrating We show whichever toolbar settings are applicable to the current tool, and hide those which are not.

You mean like a web page version of Paint.NET? That will never happen. It wouldn't work. Plus, I don't want to, I'm not interested in developing web pages.

Yes. Thanks!

Here's a very early teaser: *ducks*

aatwo, If the updater just won't cooperate, you can always get it straight off the download page ... http://www.eecs.wsu.edu/paint.net/downl ... l#download Just download and run the installer, it'll take care of the details of updating. (all the updater does is download the same thing and run it with a /skipConfig command line switch or whatever, there's not much really "special" going on )

Actually I just talked to Chris about this, he says it won't be hard to do. Let's see if we can't hold him to that ... :wink:

Yes.

Because it had to go next to a 2048x2048 image. And "smooth vs. sharp" is already implemented

Moved to General Discussion

From what I understand Emboss can be useful when working with textures for 3D games or something, for creating bump/normal maps.

I voted Yes because it's kinda true sometimes. We use GDI for font rendering in v2.6x. This has a "sharper" look than what you generally expect from an image editor. This usually looks great for UI, but not for pictures. Sometimes it looks like it isn't anti-aliased, although if you zoom in you can see that it is ... but just barely. At large sizes fonts tend to not be anti-aliased at all, which affected me when doing some Segoe UI text at size 1376 (I'm not joking here ). v3.0 will have the ability to use "smooth" or "sharp" text rendering, with the default being smooth. "Smooth" employs GDI+ for the rendering. It looks great, too.

Heck, I'd like the PDN

Moved to General Discussion Please keep posts in the right area of the forum.

What SearedIce said. You've turned off Alpha Blending. We're making this harder to accidentally disable in 3.0.

Nick, you're jumping to conclusions here. Donations do go to EECS WSU. The advertisement is an investigation/experiment, it expires on July 10th at which point we're going to figure out where to go from there. I agree it can be confusing to have both donations and an ad. Edit: investigation/experiment ... either way

Well, JPEG is a lossy format, and this is to be expected. I highly recommend using PNG instead.

I deleted the wrong one by mistake. Please reply to this post and repeat it.

Yeah I think this was brought up very very recently in fact. In fact, it's in the post right below this one ("Move small selection"). The technical explanation is that, like you said, the hit-testing is performed based on where the cursor is "on the image". We don't currently have a consistent system for keeping tracking of floating point coordinates in document space. Anyway, I'm planning to fix it for 3.0, it catches me all the time when trying to resize small selections.

FYI, I've added an entry to the FAQ detailing the ad and the "crl.usertrust.com" / "spyware" issue that pops up every once in awhile (no, Paint.NET is not spyware).

The specific details are dependent on the arrangement, but you get the idea. Anyway, given the choice between charging users for Paint.NET, or accepting donations and showing an ad in the setup wizard, I've opted for the latter.

See above: (Also, OneCare wasn't added to Paint.NET -- just a link to the OneCare website -- not sure if that was a typo on your part or not) Sorry, I forgot to filter out Win2K (much like how the ad only displays in English/US, it could also be targetted base on other criteria). OneCare does indeed require XP. In any event, Paint.NET will not become adware -- at least, the main application will not contain ads, nags, etc. However, having an ad in the installer may allow us to pick up some much needed cash without costing the users (i.e. you) anything.