NinthDesertDude

Plugins are executable self-contained pieces of code registered into paint.net via a DLL. Custom user resources are dependent data, like palettes or shapes

It won't get implemented in any case. Just not enough demand, and not enough idle time to burn. PDN only has I think 3 authorized contributors all-told, and they're pressed as it is.

There's no spray can tool in paint.net, but you can use the noise effect within a selection to get a really basic version. You could also make a big zone of noise and then use clone stamp to copy it around sort of like a primitive version of spray can. Alternatively, I have a plugin called Brush Factory that lets you choose a brush picture and draw with it. It has options for Random Horizontal Spray and Random Vertical Spray that replicate a spray can effect pretty well.

Yeah it's versioned all the way out, I just don't have the link shared everywhere and maybe I should https://drive.google.com/drive/folders/0B6r81tGW7hODamRJTlh5cnVRdk0?resourcekey=0-Y-Q8BXn0rPSPrelbIW22Bw&usp=sharing

I'm pretty sure there's no OCR plugin for PDN yet. Character recognition is a fairly specialized and difficult task. Any plugin someone would write is just going to link off to a website somewhere, so your best bet is to find something online for it or in another program.

Thanks for confirming

I think this is probably the culprit I'll try updating links to my downloads now

I've attached a copy of it to this message for you. All effect plugins are installed the same way, by dropping things in the Effects folder, usually located at C:\Program Files\paint.net\Effects (or wherever else you've installed or placed paint.net). Open the zip by clicking on it and you should be able to just drag the .dll to the Effects folder, then restart paint.net. Replace Colors V1.0.zip

Also consider the use of Parallel.For() if you're copying a large bitmap and you're not delegating this to a GPU yourself (which I imagine you're not in your plugin)

You could be clever with assumptions that are correct and likely never to change, but why bake in an assumption? Do you really lose anything by using Stride? If in the future, paint.net adds overloads to deal with lower-bit data or something like that, the image format and therefore stride may be different. But since the API is already exposed with the expectation that you're using Stride, there will be no accommodation for your plugin when those changes roll around; it will simply stop working at that time. You only lose the time spent resolving a variable, which is fractions of a single millisecond (at best)

it's not great for tablet drawing so all the drawn styles are more or less not going to happen. That leaves mostly digital stuff like 24-bit, pixel art, and whatever photomanips you get with filters

I know that brush stroke history will not include strokes that cover zero region (outside canvas or selection). Perhaps after a user finishes a meaningless brush stroke, if there's an active selection then there could be some kind of visual cue for it. This would cater directly to fixing UI friction, so it'd be worth jotting down somewhere I think. Correct me if I'm wrong though

To be fair, if it was screenshotted outside of 100% zoom, I wouldn't have been able to compare fonts to match tahoma 8pt to it. Meaning this was screenshotted at 100%, so it's not a viewing artifact. I'm not really sure what it is. But to Rick's point, if you upload the exact same file as a png (instead of a screenshot of how it displays for you) and let us look at it, that would rule out driver display issues too. I suspect something else is going on and it's neither zoom nor your GPU drivers.

Are you screenshotting while zoomed in? Is your image DPI not the normal 96? For others: this is Tahoma 8pt font with no anti-aliasing.

Can't make requests to have others do an image editing task here. If you want help with how it might be done, you can ask that though. There isn't a lot of advice to be had either way. Basically use clone stamp over the letters with a wood texture so it looks like they were never there, then edit the letters to look like gibran 27. Problem is there's no easy trick for any of this. Blur shadows when done, add tiny dots and edge highlights, etc. to letters.

No pictures/photos/references, all PDN. Lots of blend modes, tricks and some rare effects (polar inversion, quantize, ...)

Thanks for the heads up! I think in that case I'll just let this go unsupported going forward. It didn't take off, certain effects hang the app due to how they handle threading, and ultimately you can perform 2 extra steps to make this pretty much obsolete. I'm going to end up cannibalizing this code for Brush Factory anyway some day to add blending modes and whatnot, so it's not a total waste

I'm leaning towards it doesn't like your tablet, then.

Never heard of the native point input setting. When I turn it off, I can actually use the tablet with paint.net. That's new on me. But even with that off, I still get my plugin behaving normally. I'm not sure if it's an issue of your driver working better than mine, or your driver not conforming to whatever the tablet reading code in Brush Factory expects. If you were using Huion or Wacom, I'd guess it's my plugin that's in error, but you're using one I've never heard of before, so it's a real possibility your tablet isn't detected right. How about pressure sensitivity, can you make brush size change based on pressure sensitivity or something and see if it works? That would tell me a lot actually.

Huh, I thought paint.net still didn't have tablet support. Is it just running off of Windows Ink outside of paint.net or something? In my case tablets do nothing and I can't even move the cursor with it in paint.net (it works everywhere else for anything else though). If paint.net actually does support tablets already, let me know

Nearly done with initial V3 updates. Highlights: - interface improvements, a few convenient new keyboard shortcuts, and a tool selection menu - new eraser and set symmetry origin tools, new multipoint symmetry mode, automatic brush density handling for finer lines - tablet pressure sensitivity with controls to bind it to affect settings (older demo here) - custom brushes to save your settings (the old "custom brushes" is renamed to "custom brush images") - subpixel rendering to reduce artifacts - canvas rotation support and mild performance gains - the start of blend modes, currently normal and overwrite mode are supported

@Ego Eram Reputo Hey, I've got a really really early version of this change done enough that it will hopefully not break on your side of things. Try it here: https://drive.google.com/file/d/1P3lz5c63fmKgz-h_6U1_8tVNCb4OWgSC/view?usp=sharing I switched from tabs to expandable sections in the UI since I would've had to add another tab and there'd be two lines of tabs, which is horrible. Plus it's much easier to just move things around. Let me know any thoughts you have about tablet functionality, the UI, etc. Things to know: - The WinTabDN dll file is what makes tablet recognition possible. Place in Effects folder with the other - All tablet pressure controls go from no effect at 0% pressure exerted to full effect at 100% pressure exerted (the range isn't stated anywhere though) Known issues since I only spent 2 days on this so far: - tabbing through buttons is messed up right now - new buttons don't have tooltips at the bottom bar yet. Sometimes I wonder if anyone sees that bar anyway - panning with tablet or using any of the tablet buttons isn't done yet. Trying to close the BrushFactory window via tablet click will fail - the rapid change in pressure when setting or removing the stylus from the draw surface plays ugly with pronounced pressure-sensitive effects a user may set Let me know what you think Ego and everyone else, and if you have problems. I want to rule out any major tablet issues before starting to polish things.

Hey all, I don't have a ton of time these days, but after getting the last two updates in from toehead and xchellx (fantastic bugfixes, guys!) I decided to try getting tablet support for BrushFactory once again. I tried a different tact, found a library pretty quick and started integrating things. Long story short, about 6 hours and I've got things working decently, including pressure sensitivity! Tested on my Huion tablet, so that's a good start. I'll need to set up the GUI to allow people to make use of pressure sensitivity so they can map it to brush size, transparency, hue shift, etc. to get flexibility similar to photoshop or krita. When I'm all ready, I'll ask people to test with their own setup and after fixing bugs, I'll release. Positive news for tablet folks.

Luckily I check this site every other day or so and you pinged me, so I'll get to this now. Thanks a ton.