• Content count

  • Joined

  • Last visited

Community Reputation


About silverhammer

  1. I'm actually trying to make a new version of this plugin currently. The problem is that I currently only know how to use Code Lab and I need to use HSL values, which Code Lab can't access directly to my knowledge. Can anyone help me out here?
  2. I really dig a lot of the new features and the new design. My one caveat (though maybe this is just me): the new version seems to be slower than the previous version when working with very large images (in particular, 5100x3300). In the older version there was always a long delay between performing an action and actually seeing the results when dealing with really huge images, but this delay seems to have extended significantly with the new version.
  3. Perhaps that other plugin could achieve the same affect, though you'd have to tinker with a bunch of options first. I guess if you want something simple then mine is more streamlined to use. I put it in adjustments because my plugin is essentially a "Black and Transparent" plugin so I think it makes sense to put it in the same menu as the "Black and White" adjustment.
  4. This plugin is like a more useful version of the color replacement tool. Whereas the standard tool merely paints over pixels if they're close enough to the secondary color, this plugin recolors every pixel a different amount based on how similar it is to the secondary color. For example I'll use this colorful image: Here's the built in tool replacing pink with cyan at about 30%: Notice the ugly, harsh edges and how some pinkish parts of the image are entirely untouched. Now my plugin replacing pink with cyan: No more ugly edges! My plugin changes all pixels of the image based on how similar each is to the secondary color. *Threshold changes how strongly pixels are recolored based on how similar they are to the secondary color *Roughness changes how quickly the recolor effect falls off after the threshold is passed when continuous replacement is selected. Lower values look 'nicer' but tend to give the image an overall tint *Continuous replacement recolors all pixels different amounts and looks really nice. Cutoff works similar to the normal tool as pixels over the threshold are not recolored at all - recolored pixels however are colored more 'accurately' than with the built-in tool. Note that this plugin works like the built-in tool inasmuch as the color used and the color replaced are the primary and secondary colors in the palette, respectively.
  5. This is my first plugin and though it's pretty basic (and might have been done before), I think it's useful. Essentially it takes a black and white image and converts it to a "black and transparent" image. The whole point is that if you have a sketch, applying this plugin will make all of the white parts transparent so that you can color it, add a background, whatever.
  6. Only the PDN format stores the color of completely transparent pixels. All other formats set transparent pixels to black, not just TGA and regardless of RLE compression. Perhaps you could try giving stuff an alpha value of 1 instead 0 so that the color is preserved. Though I can't imagine what your work could be to require this.
  7. I'm not entirely sure what you mean. Keep in mind that RGB and HSV are two different ways of representing color. So whenever you change an RGB value, the HSV values will change and vice versa. If that's not the issue and you actually can't change colors at all, when do the numbers switch back? Is it as soon as you click on something or immediately after you type something in? Does your color palette still work for selecting colors?
  8. I can tell you that an effect like that would be very difficult to pull of in PdN.
  9. Weird, I just confirmed this. It seems to happen with many RGB values not just 255, though certain values do not change when you use the eyedropper. I can only assume that PdN stores colors in a different format than ARGB so some rounding occurs when you actually draw on the image. So I don't think that the eyedropper is picking up the "wrong" color, rather the color you're actually drawing is slightly different from the one you selected. So this bug shouldn't actually affect your drawings in any way as the visual difference between 254 and 255, for example, is essentially nothing.
  10. Here's my idea for a plugin. Basically it would let the user input equations that would take RGBA/HSV values as input and would output other RGBA/HSV values. When you hit "ok" the plugin would apply your equation to each pixel of the image individually. I know it doesn't sound that amazing but I think you could do some really cool stuff with it. For example: The equations R = B B = R would simply switch the red and blue values of every pixel. If you had a black and white image, A = 255 - V * 2.55 would make each pixel more transparent the lighter it is. It would be really handy for isolating line art. Or you could do stuff like R = R + (S / 100) * (255 - R) which would increase the redness of each pixel based on how saturated it is. I have no idea how plugins are coded, so would something like this even be possible?
  11. Working with smooth lines :AntiAliasingOn: can be a pain sometimes. They make using the fill :PaintBucketTool: and recolor tools more difficult and they're annoying to alter once they have been created. Here's a simple tutorial on how to make the creation process a lot easier while still getting the same nice results. Here are two images I made using the previous method:
  12. I added three more pictures to the original post.
  13. If you're dealing with a really large image like that, I highly recommend using Image>Resize rather than shift and drag. The result will be much higher quality.
  14. This was my first image in Paint.NET and it's still one of my favorite
  15. Eh, I liked making the signature but I'm not that into picture signatures I guess. I just try to get as much practice as possible.