Rick Brewster

I'm just not ready to invite any more people at this time. I have my hands full as it is, seriously! You have no idea how busy I've been lately, it's insane. Plus, v3.0 is currently buggy and crashy. You would probably be underwhelmed

Use the best tool for the job. Or, if it's not for a job, just use whichever you feel like using. But if you really want to fight it out, take it to The Overflow forum

Hmm actually I think I was able to fix it with a small change. But seriously the code for the Colors window is a gnarled mess. I'd love to rewrite it to be cleaner, but ... there are just so many other things of higher priority.

Here's what I've decided on: * No more updates to the 2.xx line in order to devote 100% of my Paint.NET time to v3.0. * Public, feature-complete Beta* release in December 2006. * Beta refreshes every 2 weeks until ... * Final RTW** release in February 2007. I feel these are realistic based on the progress being made and my free time availability. This essentially dedicates a full 2 months to mass public testing and bug fixing. * It will be Beta even if I release it as an "Alpha" in the name. People get weirded out if you start releasing something like "Paint.NET v3.0 Beta 8". ** RTW = "Released to Web." Contrast this to RTM which is "Released to Manufacturing". Since we have no manufacturing to do, we use the RTW acronym.

Paint.NET is not an animation editor ...

I have absolutely no idea what you're talking about.

Ok I'm gonna rip this thing apart and rewrite the logic. It's a steaming pile of junk that should've been rewritten a long time ago.

And to answer the question: Effects do not have access to Layer information. This is very intentional and by design. I don't want Effects to have access to anything but the rendering source and destination Surface objects.

Anyway you'll have to share your code. I have no idea what you're trying to do.

*bonks head* No actually it belongs in Effects API Coding, my bad.

Then this belongs in Effects API Coding. Moved

What do you mean "layer information"? Are you writing a plugin? Or do you want a metadata editor?

No problem

Actually this belongs in General Coding.

Moved to Bugs & Troubleshooting ...

Sorry

I know, I appreciate it

Dang it you're right.

Eventually It's the icon for v3.0.

I haven't posted a full-size. The full size is 2048x2048 and 20 layers or something.

But he stole my icon! (Just kidding, I don't really care, that's kinda what it's there for )

I'd love to man, I just don't have the time to come up with a design and find some place to spit out the shirts ... maybe someday? Plus, running a contest you have the risk that every single design will totally suck. Witness how every other tutorial in the Tutorials forum for awhile was basically just "whoa, run these 3 effects! isn't that trippy!"

When the UserPrimaryColor property is set, it eventually calls a function called SyncHsvFromRgb() which then does the RGB->HSV conversion and sets the controls. Unfortunately there was some code in there that was not suppressing some Changed events, and so the RGB controls were being sync'd again from the HSV stuff. So I had to add in some logic to make it ignore these changes. 15 minutes and 4 lines of code. That other bug about the PDN images opening and showing a white thumbnail took 6 times as long time fix, what a nightmare.

Mine just crashes

The magic wand stuff would be rendered in a background thread, you'd just get a lower framerate, so to speak. The goal would be to have the foreground still completely responsive and take priority over the background stuff. Once you click it'll kill off the background computation and do the 'real' computation. The biggest concern here will be memory usage. But ... honestly, at some point, you just have to require more when adding legitimate functionality.