Fisherman's Friend

Congratulations, it works fine now. Thanks for the quick fix.

:shock: Not sticky? :shock:

Got this when using EffectsLab with Film Noir: I use Paint.NET 3.20. The box appeared when clicking on "Use Effect".

Harharharharhar.

viewtopic.php?f=16&t=23271

Does "any of the plugin's effects" mean you can't get the effects from this thread "13 effects and a..." working or do you have problems with all effects available?

It's my personal opinion, but I think the "Noise" submenu should be removed. It has only three effects and I have not the closest idea which good "Noise" effect should be added in the future. - "Add Noise" should be in "Render" - "Remove Noise" should be in "Photo" - "Median" should be in "Blurs" where it was once located. It actually is a blur and I claim it was only moved to "Noise" to give the menu more then one entry (cause at this point of time, Remove Noise was not existing).

Why making it that difficult? A kind of blue would be fine, or something like the grey gradient in the background of Paint.NET itself. Actually, I just gave you the feauture suggestions you requested. I don't mind if it could be done.

The error occured in this situation: The source image is 418x984, the size of the selection seems to be unimportant. If I move the slider down the value of -18, the error occurs immediately when rendering the preview. If I use -18 or higher, it occurs when rendering the result - as far as I see it. It appears in the "+ area" as well. I never had such a problem with that plugin before. If the plugin would use IndirectUI, there would be no problem because you could work without that selection. :wink: Edit: From CodeLab to VS C# using IndirectUI by MadJik

I'd like to request to give the brushes area a different color. At the moment, white brushes are invisible.

I know it can't be done at the moment, but I would prefer that I can show/hide the layers beneath the one I draw on. Recently, I wanted to draw on certain areas of the picture, but it was required to do it on a new layer - and as you can imagine, I had to work a bit until I was able to start. Another thing which comes to my mind are blend modes - but I can't estimate if this would be a benefit. And well, I don't think it's a beta anymore. At least RC.

Use an older version of PDN for the times when you need it; run it as a 'portable' version as such. I think the point is rather that the blocking of certain plugins looks as the user is treated like a 4-year old children ("no, you are not allowed to"). Personally, I do not doubt Rick has good reasons for it (flood of emails with crash logs etc.). But I think a warning message (with "do not show again" option) or an "unprotected mode" is the better choice. The user has to decide what he wants - and he can't complain if he is informed about the consequences. However, plugins which won't run in a newer version should be blocked - anything else would be pointless.

Include pyro's tweaks: viewtopic.php?f=5&t=23253

Thank you very much! One recommendation - maybe nonsense: I'd rather do Drop Shadow in the Object submenu, which is not built-in but common if you use popular effects like Feather or Outline Object. I don't think Stylize is the appropriate place for it - considering the other effects in the menu. "Object" however comes better to my mind. Edit: Fixed an issue with the quote.

*** Paint.NET 3.20 - Not the Beta ***

Will >>this blog post<< have any positive influence on Outline Object in the future?

The effects are interesting. But do we need a new submenu just for those two effects...? I'd rather suggest to move them to "Photo". Edit: A "t" was missing...

http://blog.getpaint.net/2008/03/06/ask ... ndirectui/ If I understand this correctly, Rick is a hero.

We should just enhance the age verification. This is not the first time I have this idea.

First I had no idea how to deal with that post. Pyro answered it. Basically. I will not comment on it further. I still don't know if this issue should not be submitted to Anonymous. KrisVDM, I respect the new widening control, but this thing could also be added to the old version. And I never said something about speed. :?: Maybe we should do a little brainstorming how most of the old version can be saved. What I have to do is to do a sreenrecording showing the old version in action. Maybe I should just not update PDN, because the Fragment Blur is nothing "new" and the expanded PNG-support... Well, we have the OptiPNG plugin. PS: Is anyone interested do do a new Drop Shadow? ... Maybe... someone.. who... got... an... award...

Which version of Drop Shadow do you use? To decide it and to recieve further information, read this (scroll down the page!): viewtopic.php?f=16&t=22881&start=30

Erm, I don't know but... can someone actually tell me what the improvements of the new Drop Shadow are? This is not irony!!! (Ho-nest-ly.) And no invitation to do bad jokes! I just think the author had something in mind when he updated the plugin and I'm just too stupid to get the point! Here is the current version: This is the old version (which will not work beginning with the upcoming Paint.NET 3.30): At the moment I have to QFT this: (...) as the large majority of us are using the old version due to its more drop shadow like effect and color wheel. (...) Well, the icon is more colorful. For the coding part, this may be recommended reading: viewtopic.php?f=5&t=23064

I know. I just was kidding. Anyway, great plugin. I forgot to say that.

I know about the size. The problem occured when I used the brushes shared on the board. And it has not to be SVG. There are other vector file formats. GNA-HA-HA-HAR-HAR!!! :twisted:

Actually my effects root isn't overcrowded since the built-in effects were moved to submenus. BTW, I know it's impossible but this plugin should rather use SVGs as brushes. The PNGs become unsharp when you increase the size.