Rick Brewster

Should just need a reboot, not a forced uninstall. "Another installation is already in progress" can just mean something as simple as Windows Update doing some stuff in the background.

The MSI is generally only used when doing a network-wide deployment, like in a school or business ("enterprise") or something like that. It's not really a good option for individual installs.

This is also an error that we've seen happen when someone uses one of those "slim down your Windows install! get rid of all the bLoAAAAtttt!" utilities. If you uninstall WIA, you can't use WIA to print.

You can just hold Ctrl when you want to sample the image instead of the layer (it says this in the status bar at the bottom, btw)

Yeah this doesn't really make sense... PDN never hides the image

The diagnostics info that @Tactilis requested will tell us where this file is, and that usually gives more information about what it is. But, this is definitely not a Paint.NET bug -- HookTool64.dll is definitely the culprit.

(The term you're looking for is "canvas") This isn't currently possible but is something I'm considering for the upcoming 5.1 release. Maybe not the color but at least the brightness.

There are also these effects: https://paintdotnet.github.io/apidocs/api/PaintDotNet.Direct2D1.Effects.html The effects you can chain together are Direct2D effects. You can write a Paint.NET effect (yes the term "effect" is overloaded) that chains them together, but you can't combine Paint.NET effects like that. But that shouldn't matter because all of the bulit-in Paint.NET effects are essentially UI wrappers for the Direct2D effects. The effects whose names begin with "Pdn" are the Direct2D effects that power the built-in Paint.NET effects that you see in the app menus.

You can use Environment.GetSourceBitmapBgra32(), which will give you an IEffectInputBitmap<ColorBgra32>. Then call Lock() to get the IBitmapLock<ColorBgra32>(). Then use AsRegionPtr() to get it as a RegionPtr<ColorBgra32> which you can just index into, e.g. region[x, y]. Then just compare region[x, y].A == 255 to determine if it's opaque. Note that this works fine for querying the alpha channel, as the alpha channel is invariant with respect to color space (sRGB vs. linear scRGB vs. whatever other color profile they might have on the image!). If you want to query the RGB values, they won't line up with the color space you're using in the GPU effect, and it'll take some extra work to determine the right thing to do. So that's a topic for another time.

I kicked the tires a little, seems to work great

We do not provide any support unless you're using the latest version of Paint.NET.

Yeah it's been like this for awhile. I've been getting a steady trickle of people reporting that Ctrl+Shift+X is "broken". It's always a system with an AMD GPU

FWIW, the classic effect system is getting deprecated, and soon -- I strongly encourage you to switch to BitmapEffect or GpuEffect (or probably [PropertyBased]GpuDrawingEffect in this case). It's worth learning this now before you end up with effect code that you can no longer maintain (compile) when newer versions of Paint.NET are released. This deprecation is starting with v5.1, where the classic effect system will be marked with [Obsolete("...", false)] (compiler warning to not use it), and then in the next release (e.g. v5.2 or v6.0) it'll be [Obsolete("...", true)] (compiler error preventing you from using it). I'm happy to help with the conversion btw, just let me know what questions you've got!

Works fine here. This plugin has been around for 16 years, so if your antivirus is just now detecting it as a virus then it's a false positive.

Yeah, hi? Don't make pointless posts like this. Next time you'll be banned.