Jump to content

KrisVDM

Members
  • Posts

    154
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by KrisVDM

  1. You can get a transparent shadow with the current version already:Depending on your exact needs, the first option is to blur the shadow. That blurs the edges of the shadow into full transparency. The shadow itself is not transparent though. Your second option is to use layers. Copy the layer containing your "object" using the copy button in the layers window. Then select the bottom layer, i.e. the one you copied, not the one that contains the copy. Apply the drop shadow effect to this layer, but make sure that you turn the "Keep original image" option off. The layer will now contain a shadow only, not the "object" that created the shadow. That "object" is however still visible in the layer above it, i.e. the copy you created earlier. Now set the opacity of the layer containing the shadow, that will give you the effect you want. You can do so by editing the options on the layer. Double click the layer in the layers window, leave the blending mode to normal (or experiment with other modes!) and change the opacity. Hope this helps.
  2. I suppose this is an artefact of the the Tools, History, Colors and Layers windows being true windows: you don't see the tooltips in them or in the tool bar of the main window until you select it (e.g. by clicking its title bar). Also, the shortcuts for the tools only work if the main window is active, not when the tools window is active. And since we're at it, both "Move selected pixels" and "Move selection" show 'M' as their shortcut. Pressing M select the "Move selection tool" by the way.
  3. It seems that when "marching ants" are visible (i.e. a selection border), one CPU is fully utilized. On a hyperhtreading CPU, I see approx. 70% CPU utilization. Is this normal?
  4. Directly under C:\Program Files\Paint.NET\Effects\ (no subfolder!), place the dlls:Vandermotten.PaintDotNetEffects.dll (This one is mandatory) Vandermotten.PaintDotNetEffects.Samples.dll Vandermotten.PaintDotNetEffects.Blurs.dll Vandermotten.PaintDotNetEffects.DropShadow.dll Vandermotten.PaintDotNetEffects.Duotones.dll Vandermotten.PaintDotNetEffects.FadeEdge.dll Vandermotten.PaintDotNetEffects.Monochromes.dll Each of the effect dlls is optional, but of course, you need at least one.
  5. I agree. The background should be a solid gray. I don't care if it's configurable or not, but gray (50%-ish) should be the default and it should not be based on a windows theme color.
  6. What kind of picture are you trying this on? You need a picture with transparency for the drop shadow to have any kind of effect. So it won't do anything on a jpeg image, for example. Just to see the effect, use the eraser with a big radius (100 pixels or so) and erase part of your image. Then try again.
  7. Rick, forum posts age as well. What percentage of the posts is still relevant today? Tutorials are made obsolete by newer Paint.NET features. Posts on plug-in's are made obsolete by new versions. Anouncements are old news after a few weeks. Sure, some survive. But let the people who posted them refresh them, they'll post the good stuff on the new forum. We'll loose the noise.And the user database? For each and every one of us, it'll cost two minutes or so te register. No big deal.
  8. It's pretty stable. Give it a shot, if it doesn't work out you can alway uninstall and go back to the latest non-beta release.
  9. Planning? No, it's done. You'll need to download Paint.NET beta 2 though.Updated effects available through my blog at http://www.u2u.info/Blogs/Kris/
  10. Well, that's just the thing, it couldn't, not in a clean way anyway. (For you plug-in dev's out there: when widening and blur are used together, I effectively need an intermediate surface, and I need it in a way that scales and is thread-safe. My framework gives me that.) And the widening for the drop shadow is what started this entire thing for me: somebody asked me for it, and I just wanted to do it.But hey: Rick is "looking into" adding color picker support for effects (for dev's: a color property in IndirectUI). When that happens, you'll have an update for the Drop Shadow (and others) with a color picker within days. I promise. Kris.
  11. That was my impression as well :-( That's two votes and counting ;-)
  12. I'd rather not. That code had some significant issues, and I don't want to maintain or support it. And BTW, it won't work with a simple recompile! We basically have to recreate the color wheel ourselves, though Rick has suggested that we copy and paste Paint.NET code to do so.But you have the source code for the new one. If you can find out how to add your own property types and controls to Indirect UI let me know. I'd be glad to update the effects with color pickers. Kris.
  13. Well, to be honest, I myself miss the color wheel too, but I was hoping the new stuff made up for that, the new stuff being:- wider range for the offsets (-10..10 became -20..20) - blur is now circular instead of rectangular - shadow widening has been added And the speed didn't suffer too much. In fact, in many scenario's it's faster than the old one. Only if you combine widening and blur it can become (very) slow but hey, that ís complex stuff. If you want the color wheel back, I suggest you try to convince Rick to add support for it in Indirect UI. Kris.
  14. Rick, I don't know if you followed the discussion on viewtopic.php?f=16&t=22881, but basically they're begging and calling me names because I dropped the color wheel from the Drop Shadow UI. I know I said so before, but I believe many effects and adjustments could benefit from a color wheel (or even tow for my duotones) in the effect UI. Would you please consider adding Indirect UI support for colors? Alternatively, could you give us some pointers on how to add your own controls to Indirect UI dialogs? I haven't looked for long, but did not see an immediate way to do it. Kris Vandermotten. http://www.u2u.info/Blogs/Kris/
  15. If you want to keep the old dropshadow as well, you can simply rename the dll for the old one, e.g. to Vandermotten.PaintDotNetEffects.v2.dll. They'll appear both in your menu's then.BTW, the old one is still online (for now) at http://users.telenet.be/kris.vandermotten/Paint.NET/. I can't guarantee it will stay there for ever though... Do know that the new one has two improvements: the blur is now circular (the old one was rectangular) and the new one has the shadow widening option. And yes, the old one did have the color picker in the dialog box itself. Maybe you can all ask Rick to create a property and IndirectUI for a color? Rick, that would have to be color with bgr only, not bgra (for this effect). Many of the other effects and adjustments in this package would benefit from such a property. The alternative would be not to make effect dialogs modal but I guess the color property is a far simpler change. Kris.
  16. Believe me, I share your pain... See point 1. You need to set the "paper color" using the colors window before applying the adjustment. The same is true for several other ones. Read the summary descriptions on my blog again. Well, their point is in the source code. What I really wanted to do is create a framework for others to write effects more easily. And so I included some very simple samples. But you're absolutely correct: to an end user they're completely pointless. See point 2 above. Note that the duotone ones need two colors. I personally think that the "duotone ink on paper" is one of the most useful ones in the lot (together with the drop shadow and the smart blur - that works miracles on scanned images from magazines and such). Well' date=' its a blur that averages all pixels within a certain radius, where each pixel counts as much as any other pixel. In a Gaussian blur, the center pixels have much more weight than the further ones. But the truth is, I needed this blur for the drop shadow and since I had it anyway, I just made it available by itself as well. It's strange how these things go... To me, that was one in the very simple sample code category. No idea. What's surface blur? Point taken. Expect an update in a few days that will fix this. Point taken too. See point 8. Thank you for the constructive feedback. I did this as an experiment, to play with all kinds of C# 3.0 stuff. But it's nice to here people actually like (some of the) results.
  17. Indeed, delete the files in the demo folders (and in those only!) for the effects you don't need from the project, or edit the .csproj file directly.To change a submenu, modify the third parameter in the constructor call. For example, change public SmartBlurEffect() : base("Smart Blur", Resources.SmartBlurImage, "Smart Effects", EffectFlags.Configurable) to public SmartBlurEffect() : base("Smart Blur", Resources.SmartBlurImage, "Blurs", EffectFlags.Configurable) Kris.
  18. All colors in all effects are controlled by using the colors window before starting the effect/adjustment. That applies to the shadow color too. I did it that way for a number of reasons: it's in line with the built-in effects; the colors window is more powerful than anything I can provide in the dialogs, IndirectUI doesn't support it and the dialog box for the drop shadow had become big enough already with the new widening radius. I guess the lack of support by IndirectUI is the killer argument here. Rick? About the submenus: you do have a point and I did consider placing the effects "where they belong". Their are pro's and con's either way. At least this way the demo adjustments don't clutter your adjustments menu. If you're a developer, feel free to change the source code to move the effects around or remove the ones you don't like, just don't redistribute the modified source or binary. And about the "smart" thingy: the base classes needed a name, and in a way, they are "smart" in the sense they do take away a lot of the programming complexity. But I guess I got my inspiration from Jan Tielens' SmartPart. Kris.
  19. I've created to framework to ease the development of effects for Paint.NET. It comes with full source code and 13 demo effects, including a new and more powerful version of my earlier drop shadow effect, two duotones and a smart blur. Read all about it, or download the effects via my blog at http://www.u2u.info/Blogs/Kris/. Enjoy. Kris Vandermotten
  20. UPDATE: Version 3.8 of my effects is released. This release adds two effects, Gridlines and Object Align. All effects have significant speed inprovements, especially Drop Shadow. Many have usability improvements as well. All effects are also translated into Russian and Dutch. Special thanks to xmario for helping me with the Russian translation of these effects. Thanks also to moc426 for allowing me to release an Object Align effect. Effects per category: Drop Shadow: The "Drop Shadow" effect, under the Object effect menu. With offset, widening, blur, opacity and a color picker. Duotones: "Duotone Light" and "Duotone Ink on Paper" adjustments. Monochromes: "Cyanotype", "Sepia 2", "Grayscale on Colored Paper" and "Monochrome Ink on Paper" adjustments. Blurs: "Average Blur" and "Smart Blur" effects, under the Blurs effect menu. Color Accent: "Color Accent" adjustment. Fade Edge: "Fade Edge" effect, under the Photo effect menu. Gradient: A four-color, non-linear "Gradient" effect, with high quality color dithering. Gridlines: Draws a grid with horizontal and vertical lines, under the render menu. Object Align: Aligns the object in the selection to the selection. This version contains an installer. Just run the installer, it will ask you which effects you want to install and copy the required dll's into the Paint.NET effects folder. It will make no other modifications to your system. Please note: Paint.NET version 3.5.2 or later is required. Download (installer version for Classic paint.net) >>users.telenet.be/krisvandermotten Download (zipped DLLs for manual installation with Store version of paint.net) >>Zipped DLLs Store version installation Leave your reactions here in the forum.
  21. The user interface to the gradient effect is really very good, especially the use of handles. The line/curve tool has them too, and the text tool has a similar feature. Are there any plans to support handles on the rectangle, rounded rectangle and ellipse tools as well? I assume the Freeform Shape tool could use something along those lines too, although I'm not sure what I would want that to look like. PS. I'm sorry if this was asked before.
×
×
  • Create New...