toe_head2001

@CybOn, your hard drive is at capacity. You should delete or move some stuff off of it.

Are you using Window Blinds or something similar?

Yes, your installation of the .NET Framework is broken. Since v4.8 is built into Win 10 1903, you need to run the System File Checker. https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker

Yours shows a property named AccentColorInactive that Rick's didn't.

Can you post a screenshot of paint.net showing your selection?

And you're using the code from here?

Um, that's exactly what the plugin does.

If you want to switch to CodeLab, all you need is this: void PreRender(Surface dst, Surface src) { Rectangle selection = EnvironmentParameters.GetSelection(src.Bounds).GetBoundsInt(); string selectionCoords = "X: " + selection.Left + ", Y: " + selection.Top + ", Width: " + selection.Width + ", Height: " + selection.Height; Services.GetService<IClipboardService>().SetText(selectionCoords); } void Render(Surface dst, Surface src, Rectangle rect) { dst.CopySurface(src, rect.Location, rect); }

For the output string change: string selectionCoords = $"{selection.Left}, {selection.Top}, {selection.Width}, {selection.Height}"; To: string selectionCoords = $"X: {selection.Left}, Y: {selection.Top}, Width: {selection.Width}, Height: {selection.Height}";

: base(StaticName, StaticIcon, SubmenuName, EffectFlags.None) To: : base(StaticName, StaticIcon, SubmenuName, new EffectOptions { Flags = EffectFlags.None })

Sorry, no. Due to the different licensing of the plugins, it would a difficult endeavor to put together legally. Who would want all of the plugins anyways?

Yes, but technically that plugin uses the HD Photo format. There are differences (so I've read) between Microsoft's HD Photo and the standardized JPEG XR.

JPEG XR isn't working on my Windows 7 box.

That post gave incorrect and unhelpful information, so I removed it to prevent future confusion.

It did indeed change recently. More info here: https://blog.getpaint.net/2019/07/13/paint-net-4-2-is-now-available/

Sounds like you have an existing paint.net installation that has become broken. You can use this utility to remove the broken installation: https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed Afterwards, you can install paint.net anew.

"confirm" and "seems" are working against each other here. You mean the image you're using for a mask? Sure, if you think it will help.

Where (what program) are you copying your images from?

Yeah, I've seem them swap positions. I figure it's just the sorting algorithm that .NET is using. They have identical names, so there's no "proper" order. When the menu are sorted, sometimes one gets places first, sometimes second. No big deal.

Here's one possible solution, and it would retain the easier way too. #region UICode RadioButtonControl<Positions> position = 0; // [1] Image Position|On the Left|In the Center|On the Right #endregion enum Positions { Left, Center, Right } void Render(Surface dst, Surface src, Rectangle rect) { switch (position) { case Positions.Left: // Code Here break; case Positions.Center: // Code Here break; case Positions.Right: // Code Here break; } dst.CopySurface(src, rect.Location, rect); } If RadioButtonControl<TEnum> is too clumsy or confusing, a person could just continue using RadioButtonControl.

Are you using an Alpha Gradient or a Color Gradient? Can you post your gradient image?

Possibly, but it would probably be a bit clumsy. But using numbers is clumsy too... I do have idea on how to do it though, and it would require you to define an enum for each RadioButtonList or DropDownList. (right now, CodeLab generates these enums for you) In Visual Studio it's much easier to use enums with RadioButtonList and DropDownList. In CodeLab, the values are just cast to numbers, because that's the easiest thing to do. (Because CodeLab generates the enums for you "behind the scenes", you have no way of knowing what they're named when you're working in the CodeLab editor.)

Indeed. Fixing for next release.

Seems to work fine for me. What issue are you seeing specifically?

At work you're using Win 10 2016 LTSB/LTSC At home you're using Win 10 1903 Perhaps Microsoft changed something in Windows 10 within those 3 years. I have no idea. I guess you'll find out when you upgrade to 2019 LTSC at work. You're using that same PDF printer at both home and work?