Rick Brewster Posted March 13, 2008 Share Posted March 13, 2008 Please note that this is a beta, and expires in 60 days on May 11th. You can get this by downloading it from the website, http://www.getpaint.net/ (no need to uninstall your current version, it will figure it all out for you), or via the built-in updater. For the latter, go to Help -> Check for Updates... and make sure you are set up to receive betas by clicking on the Options button and ensuring that "Also check for beta releases" is checked. Then close the dialogs and click on Help -> Check for Updates... again. Changes since Beta 1: * Changed: Most effects and adjustments, including plugins that use IndirectUI, have been visually refreshed. The new look is cleaner and more compact. These changes are shown in more detail at http://blog.getpaint.net/2008/03/10/cle ... tnet-v330/* Fixed: Thumbnails for PDN images now include transparency, which improves their appearance in Windows Vista.* New: For developers, added a Color Wheel control to IndirectUI for use in effect plugins.* New: For developers, added ability to customize certain properties of the effect configuration dialog via IndirectUI. The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Rick Brewster Posted March 13, 2008 Author Share Posted March 13, 2008 For comparison, here is how Radial Blur looks before and after the visual refresh of IndirectUI : And, I really like how it simplifies the look of even simpler dialogs such as Brightness & Contrast: The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Ed Harvey Posted March 13, 2008 Share Posted March 13, 2008 A maintenance release of the 'Ed Harvey Effects', updated for Beta 2, is available HERE Link to comment Share on other sites More sharing options...
DRILL Posted March 13, 2008 Share Posted March 13, 2008 I've lost splatter and drop shadow don't working Link to comment Share on other sites More sharing options...
david.atwell Posted March 13, 2008 Share Posted March 13, 2008 I've lost splatter and drop shadow don't working It's still a BETA. These things happen. The authors are working on plugin updates, but if you still want those effects, you'll need to downgrade back to 3.22 until the stable is released. Â The Doctor: There was a goblin, or a trickster, or a warrior... A nameless, terrible thing, soaked in the blood of a billion galaxies. The most feared being in all the cosmos. And nothing could stop it, or hold it, or reason with it. One day it would just drop out of the sky and tear down your world.Amy: But how did it end up in there?The Doctor: You know fairy tales. A good wizard tricked it.River Song: I hate good wizards in fairy tales; they always turn out to be him. Link to comment Share on other sites More sharing options...
jerkfight Posted March 13, 2008 Share Posted March 13, 2008 This cleaner look, looks well a lot cleaner, but i think i'm going to wait for a while due to plugins  Link to comment Share on other sites More sharing options...
I Like Pi Posted March 13, 2008 Share Posted March 13, 2008 "View Plugin Load Errors" in the file menu doesn't seem to work for file type plugins. Because of a change in the name of the methods, my ASCII plugin broke, but the error menu item was not shown. Link to comment Share on other sites More sharing options...
DRILL Posted March 13, 2008 Share Posted March 13, 2008 I've lost splatter and drop shadow don't working It's still a BETA. These things happen. The authors are working on plugin updates, but if you still want those effects, you'll need to downgrade back to 3.22 until the stable is released. I just want help Rick Link to comment Share on other sites More sharing options...
pyrochild Posted March 13, 2008 Share Posted March 13, 2008 I've lost splatter and drop shadow don't working It's still a BETA. These things happen. The authors are working on plugin updates, but if you still want those effects, you'll need to downgrade back to 3.22 until the stable is released. I just want help Rick When our plugins break, it's not generally not Rick's problem. It's the plugin authors'. Usually. But the times when it is Rick's problem usually get caught and fixed before a beta is even released. ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
david.atwell Posted March 13, 2008 Share Posted March 13, 2008 I just want help Rick When our plugins break, it's not generally not Rick's problem. It's the plugin authors'. Usually. But the times when it is Rick's problem usually get caught and fixed before a beta is even released. So, thank you for your help, but it's covered. :-) Â The Doctor: There was a goblin, or a trickster, or a warrior... A nameless, terrible thing, soaked in the blood of a billion galaxies. The most feared being in all the cosmos. And nothing could stop it, or hold it, or reason with it. One day it would just drop out of the sky and tear down your world.Amy: But how did it end up in there?The Doctor: You know fairy tales. A good wizard tricked it.River Song: I hate good wizards in fairy tales; they always turn out to be him. Link to comment Share on other sites More sharing options...
Rick Brewster Posted March 13, 2008 Author Share Posted March 13, 2008 "View Plugin Load Errors" in the file menu doesn't seem to work for file type plugins. Because of a change in the name of the methods, my ASCII plugin broke, but the error menu item was not shown. The menu item is only hooked into effect plugins. It's called "plugin load errors" so that I could add file type stuff to it if I wanted to. File type plugins are actually not even discovered and loaded until the first time you use a Open or Save dialog. The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pyrochild Posted March 14, 2008 Share Posted March 14, 2008 *sigh* I miss the crash button already.... ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Rick Brewster Posted March 14, 2008 Author Share Posted March 14, 2008 *sigh*I miss the crash button already.... Eh? Why? The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pyrochild Posted March 14, 2008 Share Posted March 14, 2008 I was kidding ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Rick Brewster Posted March 15, 2008 Author Share Posted March 15, 2008 Oh, I was just making sure there wasn't a legitimate reason you would want it or ... something. The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Mike Ryan Posted March 15, 2008 Share Posted March 15, 2008 This really might sound odd, but is there any way to overide Paint.NET from blocking plugins? Feel free to PM me if you dont want to publicaly announce it, or ignore me if you could care less Link to comment Share on other sites More sharing options...
Simon Brown Posted March 15, 2008 Share Posted March 15, 2008 This really might sound odd, but is there any way to overide Paint.NET from blocking plugins? Feel free to PM me if you dont want to publicaly announce it, or ignore me if you could care less Why would you want to? The only two ways I could see would be to modify the pdn source - or decompile and plugin and change the class name (assuming that is how pdn identifies them to block). Link to comment Share on other sites More sharing options...
Mike Ryan Posted March 15, 2008 Share Posted March 15, 2008 This really might sound odd, but is there any way to overide Paint.NET from blocking plugins? Feel free to PM me if you dont want to publicaly announce it, or ignore me if you could care less Why would you want to? The only two ways I could see would be to modify the pdn source - or decompile and plugin and change the class name (assuming that is how pdn identifies them to block). I really cant believe I am asking for it myself, but I NEED GreyCStoration. There are certain elements that I need on a work I am doing atm. Link to comment Share on other sites More sharing options...
Myrddin Posted March 15, 2008 Share Posted March 15, 2008 I really cant believe I am asking for it myself, but I NEED GreyCStoration. There are certain elements that I need on a work I am doing atm.Use an older version of PDN for the times when you need it; run it as a 'portable' version as such. How to Save Your Images under Different File Types My dA Gallery Link to comment Share on other sites More sharing options...
Fisherman's Friend Posted March 15, 2008 Share Posted March 15, 2008 I really cant believe I am asking for it myself, but I NEED GreyCStoration. There are certain elements that I need on a work I am doing atm.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. Link to comment Share on other sites More sharing options...
Simon Brown Posted March 15, 2008 Share Posted March 15, 2008 I think the point is rather that the blocking of certain plugins looks as the user is treated like a 4-year old children I imagine its because the new plugins are still kept when upgrading - and RB really doesn't want to include any configuration options. Link to comment Share on other sites More sharing options...
Rick Brewster Posted March 16, 2008 Author Share Posted March 16, 2008 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. What Paint.NET really needs is a plugin system that incorporates features for easing installation, organization, isolation (plugin crash = only crashes plugin, yes these still happen), updating, etc. I'm looking into this for 4.0, because if I do this in the 3.xx code base there are two problems: 1) I have to implement it twice because the effect and file type extensibility systems are totally different (I would unify this stuff for 4.0), 2) It pushes back work on 4.0 even more (I estimate that every hour I spend on 3.xx pushes 4.0 back by 2 hours). Honestly, the plugin system was originally designed as a "hey cool, you can do that in .NET" feature, with no real human factors taken into account. The fact that it has become this popular is amazing and scary Kinda like having a big tax bill because you made a ton of money, "Gee I wish I could have that problem..." The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pyrochild Posted March 16, 2008 Share Posted March 16, 2008 This really might sound odd, but is there any way to overide Paint.NET from blocking plugins? Feel free to PM me if you dont want to publicaly announce it, or ignore me if you could care less Why would you want to? The only two ways I could see would be to modify the pdn source - or decompile and plugin and change the class name (assuming that is how pdn identifies them to block). To get around the block, you just need to bump the minor version number. (Major.Minor.Revision.Build)* You can probably do that via reflection. You can definitely do that with a recompile. But Rick only blocks plugins if there is a good reason... ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Rick Brewster Posted March 16, 2008 Author Share Posted March 16, 2008 But Rick only blocks plugins if there is a good reason... Like when Film v1 was causing DEP errors and making .NET cry The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pyrochild Posted March 16, 2008 Share Posted March 16, 2008 When plugin authors release fixed version of blocked plugins, do you scrub the blocklist or leave 'em? Nevermind, that was a stupid question. Of course you leave 'em. But Rick only blocks plugins if there is a good reason... Like when Film v1 was causing DEP errors and making .NET cry I still don't understand how it could possibly cause a DEP... ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Recommended Posts