toe_head2001

Did this crashing start when you installed Windows 10 1803 (April 2018 Update)? Are your Nvidia drivers up-to-date?

Not if you have paint.net set as the default editor for those filetypes; which can be done by the paint.net installer.

Okay, but compatible filetypes already have the 'Edit' context menu item. Though it lacks the icon and "... with paint.net", it works fine.

Version 1.6 posted. Previously, the effect would increasingly go slower as the Margin increased. Now the effect increasingly goes faster as the Margin increases! I've also moved the Anti-aliasing checkbox directly below the Radius slider.

Good. That means it's working correctly. You should go back to the first page, and re-read what it says. Sorry, we will not be making older versions available. Nor is it open source.

Sorry, but you should not be distributing unofficial packages of paint.net.

This seems to be correct, as the attached version matches with what's in the changelog.

I'm pretty sure that's how it's supposed to work. You generated those .msi files (albeit with the tools provided in installer). Therefore, the signatures shouldn't be valid. I fail to see why this matters. Since you generated the files, you know they're legitimate. The msi files should only be used for your (or your organization's) own use, and not redistributed.

Why remember when computers can remember for you?

It's one of the attachments that lost its filename and extension. It's still a valid zip though. I've gone ahead and reattached it, so people won't have issues with it.

Version 1.4 posted. This adds a built-in Russian Translation, and defaults the Font dropdown to Arial.

Other features have had higher priority. It's as simple as that. I don't know... Why haven't you created one yet? You've had like 10 years already to work on it!

Technically, you had to move your mouse over the left-hand ListBox to trigger the crash. Oh wow, that was silly of me. I was using an index in the line just before its bounds check. Fixed. Version 1.2.1.2 posted.

Oh, that's what you meant... Cascading windows Multi-Document Interface. Yeah, that has nothing to do with the checkerboard, hence our confusion with your question.

I think either your line images are too small in resolution, or you're mixing raster images with vector images. Can you give use some more details. Cropped screenshots don't tell much.

Those lines look antialiased to me.

Please show us an image of the issue.

Ensure that antialiasing is enabled. https://www.getpaint.net/doc/latest/LineCurveTool.html#10

I don't think there's a lack of interest; it's just a very difficult object. Lots of textures and what not. The last last two rounds (Kitchen Knife and Vase) had plenty of entries; especially Vase. I think a little more discretion just needs to be used when setting the object. Don't be afraid to say no to an object; just be nice about it. I had to do it a few times when I was the host. Objects with simple geometric shapes tend to receive more entries. Compare Pencil to High Heel. My two cents.

Link fixed.

Adding support for the Dark Theme is very easy, and only takes a few minutes. The first step is to set the UseAppThemeColors property in your EffectConfigDialog to true. This can be done using the Properties pane in Visual Studio: This will automatically set the ForeColor and BackColor of your Form based on the active PDN theme, and most of the child controls will simply inherit those color values. There are some special cases though. For Buttons (ex: OK, Cancel), you'll want to set their FlatStyle property to FlatStyle.System. For TextBoxes and NumericUpDowns, you'll need to set the colors manually. For example: myTextBox.ForeColor = this.ForeColor; myTextBox.BackColor = this.BackColor; or if you have many in your form, you may want to use a foreach loop: public MyConfigDialog() { InitializeComponent(); foreach (Control control in this.Controls) { if (control is TextBox || control is NumericUpDown) { control.ForeColor = this.ForeColor; control.BackColor = this.BackColor; } } }

Version 2.9 posted. I've added support for the Dark Theme.

@SwankyDoodleSandy, the link to the tutorial seems to working fine for me. What exactly is the issue? What do you see?

Version 1.5 posted. I've added support for the Dark Theme.

Version 1.5 posted. I've added support for the Dark Theme, and moved it to the 'Texture' menu.