evanolds

Source code is available as of October 16, 2012. http://www.evanolds....dn_effects.html

PDN v3.5.5 Haven't seen this one reported yet Repro steps: 1) Active the brush tool 2) Set the size to 50 (helps for visibility of the problem) 3) Expand to "More" in the colors window and set the alpha to 100 4) Change from "Normal blending" to "Overwrite" 5) Draw Result: Should those white lines be there?

Posted version 3.7 which saves all images that have dimensions greater than or equal to 256 as PNGs. Please let me know if you find any problems.

I think this guy gave me a donation (or someone did), so I'll look into this.

http://www.evanolds.com/dl/IcoCur.dll I've re-added the option to save layers separately as individual images within one icon file. To do this, you will have to name the layers in the form #x# for example: 32x32 There are also some other improvements, most of which are just small efficiency improvements and may not be noticeable.

Ok, thanks for the feedback. So my first comment I will steal from Rick: viewtopic.php?f=27&t=32826 As he says, Paint.NET really just isn't made for this. I would love it if I had access to each separate document that the user was working on and then I could save one icon-image per document, allowing the user to create exact-sized, layer-based, high quality icon images. But I don't have that ability. If I'm understanding correctly, it's the fact that there's no way to currently save different images in the same icon file that's really lacking? I think no matter what changes I made the user would have to jump through some hoops to author the type of icon files that you desire. There's really no elegant way to deal with this. I have authored a separate app that can do this but I don't want to post it here so PM me if you want it. Plus, there are already a bunch of separate apps that are better suited and the problem is not that people don't know about them but rather that they don't integrate with Paint.NET. If I went down the avenue of saving different layers as different images, I'd probably want to remove the ability to make multiple resized copies and maybe even eliminate the option to save 8-bit icons. Would people miss the "Copies to be saved" dialog if I removed it and introduced the requirement of naming your layers appropriately or perhaps having transparency to the left and bottom of your layers' images to determine the size? I would think that this would make icon editing a lot more difficult for those that don't need a finer level of control. This plug-in already violates both the loading and saving rules of PDN because it uses a custom dialog prompt for both. I didn't have a lot of compliant options for authoring this plug-in. In terms of loading and saving, I can't access multiple PDN documents because that is not supported (according to Rick). I can't have a separate app pull in the images directly from PDN (without a copy/paste or save) because there is no plan for interprocess communication mechanisms in PDN (according to Rick). For saving, I can't have an "append mode" where the user saves an icon and then saves again with the same file name and it just writes the new image, leaving the existing ones in the file, because the save code path in PDN always clears out the destination file to 0 bytes first. I've been going through the plugin code and it has a lot of older code and doesn't even compile anymore, so I'm somewhat resistant to work on it much more, but also reluctant to release the code because it's in such disarray. The danger of me updating this plug-in is that I'm likely to remove something that someone might want in order to give someone else what they want. I don't want the user to see some save prompt and say "what the heck is this" because they're looking at a bunch of different options that exist only to compensate for functionality that PDN just doesn't have. This is primarily because it would be detrimental to the average user and only benefit a small percentage of intermediate or advanced users. Glad to hear that it's easy to implement! The icon file format is simple and is outlined here: http://en.wikipedia.org/wiki/ICO_(file_format) so you could probably do that in a few days and have it for us soon . ... Alright, I have a habit of making people angry with my "subtle" sarcasm so I won't continue it, but that remark is pretty much true. The best solution for people that have very specific needs is to code up plug-ins for themselves. Such plug-ins, if not distributed, can violate any and all Paint.NET rules and can really help you get at exactly what you want to achieve. You can use reflection to find the class "EOIcoCurWriter", instantiate it, and use it to write Bitmaps to an icon file if you prefer. But please understand that it's in the interest of breaking as few rules as possible and keeping the plug-in at least somewhat easy to use that I'm deciding against these more advanced options for now.

Does there currently exist, or are there plans to have, any sort of interface that allows for the development of a file-type plugin that can load or save multiple documents at once? I could sure use this for my icon loading/saving plugin

Ok, version 1.7 with a fix for this has been posted. Good find, thanks.

I have this code to resize a surface to a new surface: Surface fitsurf = new Surface(sz.Width, sz.Height); // "surf" is also a Surface fitsurf.FitSurface(ResamplingAlgorithm.SuperSampling, surf); It fails with an ArgumentException when surf is smaller than fitsurf, which looks as though it may be by-design. Is there an argument I can pass, or a different function I can call to work regardless of the dimensions of two surfaces?

Thanks for posting this. I've found the source of the problem in a call to a PDN function. I'll ask Rick about it in the developer's forum.

Posted version 1.6 What was the Octagonal/Quadrilateral reshape/matte is now broken up into two effects: ("Distort" submenu) Quadrilateral Reshape and ("Transparency" submenu) Polygonal Transparency The Polygonal Transparency effect has a configurable number of control points in the range [3, 20]. The Conditional Hue/Saturation adjustment, 3D Object, and mirror effects are still present as well. In addition to these alterations, a small bug was found and fixed that may or may not have been the cause of the plugin being blocked in the first place.

I have uploaded a version with the changes I've made thus far. I've replaced the old file with the new version so everyone that downloads will be BETA testing whether they like it or not : http://www.evanolds.com/dl/EOEffects.dll I took the quadrilateral reshape/matte out of the of the oct/quad one and it's now a separate effect, but the old oct/quad one is there also. I'm curious to see if people see a crash in one of these if they also see it in the other. The 3D object effect no longer uses the ray-tracer but a software renderer that has known clipping issues, but these will only be noticeable when content is outside of the viewing frustum. So unfortunately this effect is still very much in the BETA stage. It also has to render to an off-screen surface and then copy this to the effect destination surface, which gives it a bit of "lag" between parameter adjustments and the start of rendering. Please report problems as you encounter them.

I'm not sure what caused the problem since I've never been able to reproduce the problem. There was something like a DivideByZeroException in the logs Rick sent me. I have some changes that I've made and everything works fine on my machine, but then again, it was always working fine on my machine. Maybe I'll post an update later, but the same problem could just come up again for all I know.

If you are considering donating (which is always appreciated ), I have a donation page that I put up today at www.evanolds.com/donate.html. This is a possibility, however this and pretty much all other options are kind of "hacks" in the sense that they're getting around the fact that Paint.NET isn't really suited for editing multiple images of different resolutions in a single document. I and several others have authored separate applications for icon editing that better serve this purpose. Now I realize that a lot of people don't want to have to download a separate utility application and they'd just like it all to be in Paint.NET. While I can't say I disagree with this, I do think that for more serious icon editing and deployment, you'll probably have to use a separate app. So I guess some questions that I'd want to ask people are: 1) Are you aware of the numerous other free applications that do icon/cursor editing? 2) If so and you're not using them, why is that? Is it just because you do the editing in PDN and don't want to do the extra step of saving your intermediate work, reopening in another app, and then resaving? Is it because you'd just rather not download another application to your hard drive? 3) If you aren't aware of them, would you be more eager to be informed about them or would you rather some sort of workaround be added to this plug-in to make Paint.NET have extended icon/cursor editing capabilities? 4) Are you happy enough with the way this plug-in is and would rather have me work on new plug-ins that do new things, instead of tweaking other plug-ins to try to accommodate the needs of the more advanced users? I assure you that these are honest questions and aren't trying to imply something by just being posed. If any current users of this plug-in can give their feedback, I'd appreciate it.

The following effect DLLs are replaced by this plug-in and can be removed if they are still in your PDN effects directory: HueSatFilter.dll Octagonal.dll