![]() ![]() I was simply listing the likeliest coding mistake that I've seen cause that to happen in the past. and I'll need to try and figure out which one it is.ĭoesn't look like a resource problem, like you say. that means either something is wrong with the plugin, something is wrong with PDN, or something is wrong with your installation. If you do all that, and still have two copies of either bricks or varicose (or both), please post here again. Verify that you have the following effects: ![]() Copy ONLY "jchunn.dll" to your effects folder.ġ0. Unzip "jchunn.zip" and verify that it contains ONLY jchunn.dll.Ĩ. you have something seriously wrong with your installation, or you didn't "really" delete the files, or your effects folder is not where you think it is, or something else has gone wacky with your computer.ħ. Verify that you do not have any of the following effects in the effect menu: Go to "c:\program files\Paint.Net\effects\" (or whereever your "effects" folder is).ĥ. If you are getting duplicates (more than one copy of bricks or varicose in your effects menu), please try the following and let me know if this fixes the problem.Ģ. but that shouldn't matter since I am still just returning a bitmap. The only thing I "am" doing that is different from the other examples I've seen posted is that I am using the "my.resources" namespace, instead of embedding the resources the way others are doing it in C#, strictly for the effect icon. If I am, let me know what it is and I'll go back to the drawing board, but this is pretty basic stuff, so I'd doubt it. If you (Rick) want to just quickly open the source and take a quick look (even in notepad if you didn't install vb) you should be able to verify that I am not doing anything out of the ordinary. It is possible that I have a reference to the resources dll, but if I do, it was simply a matter of setting the reference, and never using it. Certainly, a quick look will make it obvious that (unless I am completely missing something) I am not doing anything fancy with resources. That is vb.net, but it is very simple and easy to follow. I am at work, so I can't post the latest source, but I am not doing anything differently than what is in this earlier version, other than re-arranging some of the effect logic for the "bricks" effect: The plugin is not doing anything out of the ordinary. If so, this plugin will not work in future versions of Paint.NET. Please, please, please, please!! I would love for this tool to return in the exact same shape/functionality as it once had.Looks like jchunn is probably using PdnResources to load some text. But all I really want is for the old tool to return in it's beautiful glory once more! Is it possible that the new tool is too sensitive? I'm not sure. However, the current tool in BoltBaitPack62 feathers the object by simply removing parts of the image, which is not very useful especially if you're trying to feather a pixelated line (now the line simply disappears because of the new functionality). Previously, your feather object tool would only feather the edges of said object, leading to fantastic results and no deformities nor dilations of the base shape. ![]() But now, the functionality does not act in the same manner anymore and it's very frustrating to use (pretty much useless for my case now). I would love if you were to bring back this version of the feather object tool that you made, because it was THE most useful tool I have used in to date every time I load the program up I end up using that version. In your most recent update, the feather tool's functionality was changed to be drastically different in comparison to an older version of your pack that I was using for a very long time which does not work anymore (BoltBaitPack50, the feather tool under effects > object). There, thank you for the incredible pack! I have just updated to your 5.0 compatible version of this pack and have been enjoying it thoroughly! However, there is one thing that is bugging me significantly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |