null54

No, but I can link to a few. https://resources.psdbox.com/photoshop/flying-birds-photoshop-brushes https://resources.psdbox.com/photoshop/sun-rays-free-photoshop-brushes https://www.brusheezy.com/brushes/2187-24-clouds

Fixed: Handle missing directories when loading brushes I am not able to reproduce that.

I do not have any information about when this plugin will be integrated into Paint.NET. I added the line from the first post in this thread to the readme, and updated the project readme on GitHub.

Fixed: Use FileMode.Create when writing the settings Another pull request: Fix the default brush loading After reading the linked thread I am wondering if GDI+ may be converting the 32bppARGB images to 32bppPARGB as part of its internal processing. This would make sense if it is calling any GDI functions because 32bppPARGB is the only 32-bit alpha channel format that GDI supports. It also appears to be fairly well documented that GDI+ performs best when it is using 32bppPARGB, a few links below as examples. This could indicate some kind of format conversion is being skipped. https://richorama.github.io/2016/08/10/image-interpolation-benchmarks/ https://www.gamedev.net/forums/topic/467752-maximizing-gdi-speed/ https://microsoft.public.dotnet.framework.drawing.narkive.com/Pb9bQRzv/great-speed-improvement-trick-format32bpppargb

@Joshua Lamusga Two pull requests. Do not create unnecessary RenderArgs instances Use a ListView for brush selection

It sounds like you may have installed the Megalo pack, which illegally bundles and redistributes plugins from this forum and is known to cause all sorts of problems. If so you should delete the contents of your Effects and FileTypes folders and run a virus scan. See the following thread for more information:

As mentioned above I am using the serialization that is built-in to the .NET Framework, and XML is what the DataContractSerializer uses.

Here is the pull request: Save the settings to a file instead of the registry I would have also submitted the ListView code, but it has conflicting changes. I have not modified any of the drawing code, so I have no idea what could be causing that. ?

My plan is to convert the registry settings to an XML file stored in the Paint.NET user files folder. This would allow the settings to be represented by a strongly-typed class, while letting the .NET Framework handle the conversion to/from XML.

@Joshua Lamusga Another pull request and a few questions. Override the On* methods instead of using event handlers I was thinking of moving the settings into a separate class to allow for storing more general settings, such as the last folder in the add brush dialog. Should the plugin store settings in the Paint.NET user files folder instead of the registry when Paint.NET is in portable mode? I have also been considering changing the "Add Folder" button in the preferences dialog to use the Vista-style folder browser, basically an Explorer open file dialog that can select folders. This would require adding a large amount of COM interop code, and even though this dialog is more user friendly I am not sure that users would browse for a folder often enough to make it worth the amount of code needed to implement it.

@Joshua Lamusga Two more pull requests: Reorganize the cleanup code: https://github.com/JoshuaLamusga/Brush-Factory/pull/10 Store the final image as a Paint.NET Surface: https://github.com/JoshuaLamusga/Brush-Factory/pull/11 I hope I am not submitting too many pull requests for minor changes.

I replied to your review and amended the commit to remove the interop code.

@TrevorOutlaw Now the crash should hopefully be fixed. No it looks like another multi-threading race condition, it amazes me how many of those I keep finding.

Actually the stable version of Brush Factory (1.6) can load ABR files. @Joshua Lamusga released that version on the 29th of October, but he did not create a new post to bump the topic in the list. The in-development version will load faster and be easier to use, due to changes in how the brushes are loaded and displayed. But as @welshblue stated you should save your work before using it as there may still be bugs that can cause it to crash.

Fixed. Also I am now including the pdb file with the effect, this should provide me with more information in the event of a crash. Both files should be placed in the Effects folder.