midora

OK, I thought it's about exchanging arguments to get a good solution.

Thanks, but you know that you just translated one sentence into four? ;-)

You are just the judge who decides what will be implemented. Not the judge who decides what's a good idea. ;-) Everything is better than writing the the dll into the Program files folder. Desktop just means that you always have to hide all windows and search where it is placed this time. Like looking for the crash log of the old Paint.NET.

See Ricks comment here

I'm happy with this change because this was the reason why I never used the save as dll functionality. But maybe you should allow to set a path (default to desktop). This could also satisfy the 'administrator' users.

Do you like to provide more detailed information about your plugin to the user of Paint.NET 4? If the answer is 'yes' then you should continue to read. All plugins which are not built-in to Paint.NET 4 are showing a small puzzle image to the right of the menu entry. If the user hovers the mouse over the plugin menu entry then a tool tip pops up showing information about the plugin. If the plugin does not offer additional information you will just see the location of the plugin in the file system. To offer additional information your plugin has to add and implement the IPluginSupportInfo interface. Add the interface to your effect class: [PluginSupportInfo(typeof(MyEffect))] public sealed class MyEffect : PropertyBasedEffect, IPluginSupportInfo Compiling your code will throw errors that some methods of the interface are not implemented: DisplayName, Version, Author, Copyright, WebsiteUri Here is an example of an implementation which takes some information out of the assembly. To access the assembly using System.Reflection; has to be added. And now the methods: public string DisplayName { get { return ((AssemblyProductAttribute)base.GetType().Assembly.GetCustomAttributes(typeof(AssemblyProductAttribute), false)[0]).Product; } } public Version Version { get { return base.GetType().Assembly.GetName().Version; } } public string Author { get { return "Barbarella"; } } public string Copyright { get { return ((AssemblyCopyrightAttribute)base.GetType().Assembly.GetCustomAttributes(typeof(AssemblyCopyrightAttribute), false)[0]).Copyright; } } public Uri WebsiteUri { get { return new Uri("http://forums.getpaint.net/index.php?/forum/7-plugins-publishing-only/"); } } An other way to implement the plugin info is to use a seperate class: public class MyPluginSupportInfo : IPluginSupportInfo { public string DisplayName { get { return ((AssemblyProductAttribute)base.GetType().Assembly.GetCustomAttributes(typeof(AssemblyProductAttribute), false)[0]).Product; } } public Version Version { get { return base.GetType().Assembly.GetName().Version; } } public string Author { get { return "Barbarella"; } } public string Copyright { get { return ((AssemblyCopyrightAttribute)base.GetType().Assembly.GetCustomAttributes(typeof(AssemblyCopyrightAttribute), false)[0]).Copyright; } } public Uri WebsiteUri { get { return new Uri("http://forums.getpaint.net/index.php?/forum/7-plugins-publishing-only/"); } } } In this case you have to add a reference to this class and not to the effect class. [PluginSupportInfo(typeof(MyPluginSupportInfo))] So now let your plugin tell us more about it...

Perfect.

Thanks for sharing. Something like this was on my ToDo list. I'm happy that you did it. Plus: You explained in the source how you are solving the issue that there is no unique solution of the problem. A variant may be to respect the surrounding pixels to decide whether you are unblending a pixel or not.

0.5: Sometimes ProgressDialog did OnLayout to early...

This thread is obsolete in the meantime. See ImPDF.Open.FileType and ImPS,EPS,AI.Open.FileType. -------- Long time ago I told in a thread that I may implement the import of PDFs via Ghostscript. So here we are. This solution is not integrated in ImPDF in the moment because the way how Paint.NET handles "save combined with load to show a preview". There will be a somehow dirty solution possible, let's see. For now if you like to test this plugin then you have to disable ImPDF. Feedback on test is welcome. PostscriptImport.FileType v0.6.zip Warning: This is a test version and not a final release. Postscript.FileType readme ========================== Imports PDF, PS, and EPS files and renders them to Paint.NET bitmap layers. This plugin requires an installed Ghostscript version. This plugin will be merged with the ImPDF plugin in the future. In the moment you have to decide if you like to use ImPDF to export as PDF or this plugin to import. These two plugins can not be installed at the same time. Sometimes the rendering of a page takes a long time. Be patient ;-) Installation ------------ - Install Ghostscript (http://www.ghostscript.com/download/). The plugin has been tested with version 9.10. If Paint.NET is running as an 64bit application then you have to install "Ghostscript for Windows (64 bit)" else the 32bit version. The plugin identifies the installed ghostscript version via the registry. - Copy the two files OptionBasedLibrary vX.X.dll/.dlc to the Paint.NET\ folder (NOT to Paint.NET\FileTypes\ !!!) - Copy the two files PostscriptImport.FileType.dll/.dlc to the Paint.NET\FileTypes\ folder - Remove other plugins supporting the same file type (.pdf) from Paint.NET\FileTypes\ folder (to avoid possible conflicts) I.e. 'ImPDF.FileType.dll' plugin. - Do not remove older versions of the OptionBasedLibrary if they are required from other plugins. Compatibility ------------- Paint.NET 3.5.11 and 4.0 Beta Supported languages ------------------- English and German Load dialog options ------------------- - Pages: Enter the number of the first and the last page of the document you like to extract. The default is all pages. If first page is larger than last page then the order of layers will be inverted. - Resolution: Because Postscript is a vector format you have to provide a resolution which defines the quality of the rendered pages. The resolution has effect on the speed of rendering and the amount of memory needed for the pages. - Antialiasing options: Typically it makes no sense to use an other value than "Strong". But "None" or "Weak" is faster. - Transparency: If set then the image is rendered against a transparent background. This is much slower than rendering against a color. Known issues ------------ - Paint.NET does not provide a load dialog template to filetype plugins. So to allow the plugin to show a dialog it delegates its dialog (derived from PdnBaseForm) to the thread of the main window. This works fine but not perfect. So you will not get an error beep if you are clicking to the main window while the ImSVG dialog is open. - If you are canceling the option dialog you will get an unspecified error. But this just means that Paint.NET has no idea about canceling the load operation. PDN4 allows you to check the error details. If it tells "Canceled by user" then no error happend. - If you try to 'Save' (not 'Save As') a loaded pdf, ps, or eps then Paint.NET will not fallback to 'Save As' automatically. The 'Save' dialog opens and shows an error. This is fixed in Paint.NET 4.0. On the 'To do' list -------------------- tbd History ------- 0.6 (7.3.2014) - Supports transparency - Better error handling if there is no matching Ghostscript version installed - EPScrop support - AI file format support (which in fact contains PS or PDF) 0.5 (3.3.2014) - Progress dialog fix 0.4 (3.3.2014) - First public release

You can use IrfanView to convert .pdn to .png. Or pdntopng by using drag and drop.

You saved the file in png format but used the extension .pdn. So if you change the extension to .png you will be able to open the image. But - sorry to say - if you used layers in the image then they are lost because png format does not support layers.

There are several ways to do this but no easy one. I'm miss-using DropShadows Widening feature to create a mask. This way you can increase the area exactly by a pixel value.

If you are doing this then please keep the old one and mark it with 3.5.11. Because the new one is Paint.NET 4 only! (It requires .NET >= 4.0).

Maybe it depends on the file. So here is a file which is always showing computing (in 3.5.11 and 4.0) if HTML or CSS is selected. FLAG_B24.zip I verified that in both cases 1.0.0.3 is in the FileTypes folder. I would prefer the change of the extension. Especially because it is not a standard user file content.

I was confused because you pointed to a thread that tells that it's working now. So I thought that I missed the update. But the reason why it is working for me is still that I copied ICSharpCode.SharpZipLib.dll from PDN3.5.11 to PDN4. That's why I don't like these exe solutions without any version number.

I downloaded a fresh version yesterday but maybe I called then an old version of the installer. I don't know. Anyway it's working for me now. Thanks.

Thanks. But now in both cases (html and css) the plugin is not able to load and does not stop computing. >>The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. There is an other thing you may think about. It's about the extension. I would prefer that the plugin uses .b64 instead of .txt. In my case .txt conflicts with a plugin which loads .txt files as bitmaps. So I always have to decide what to install.

Just a small hints. The plugin is not working in PDN 4 because Paint.NET no longer installs ICSharpCode.SharpZipLib.dll. A temporary solution is to copy the dll from 3.5.11 to 4.0. You may implement this or use .NET 4.5 System,IO.Compression.ZipFile class.

Sorry I totally missed your response. Sometimes I need a raw base64 BGR or RGB stream. But I can always use a tool to convert it. Two non-important issues: 1) If you are using file format BMP and set the HTML or CSS option then the loader part is not always able to load the file (you can also see this in the save dialog that the file size always tells "computing...". ) 2) If you are setting URI data type to HTML and then switch off DATA URI encoding then the Insert line break checkbox stays disabled. You first have to set URI data type to None. Seems to be a small issues with the IndirectUI rules.

Just out of the box because the old one has issues in 4.0 and was never complete. So I did this one some time ago. Used nowadays to allow data analysis with some special plugins. The PAM format allows more than 4 channels so you can easliy store additional parts of the spectrum.

Your file contains more than 300 layers. Because of the internal data model of Paint.NET this sums to more than 5GB. Additionally it uses layer groups and masks. So my advice would be to use GIMP.

'Portable Anymap' FileType Plugin (.PAM, .PBM, .PGM, .PPM) Summary Paint.NET FileType plugin which loads and saves image files in one of the PNM (Portable Anymap) file formats: PAM - Portable Arbitrary Map (Black and White, Grayscale, RGB; Alpha channel; raw only; up to 16bits per channel) PBM - Portable Bit Map: (Black and White; plain and raw) PGM - Portable Gray Map: (Grayscale; plain and raw; up to 16bits per channel) PPM - Portable Pixel Map: (RGB; plain and raw; up to 16bits per channel) These are quite old image formats used mainly in the academic area. They do not support any kind of packing the pixels. For more information see 'The Netpbm Formats' Author Martin Osieka Download Find the latest version of the plugin ImPNM.FileType v1.1 (19.2.2015) here. Installation Follow the instructions carefully Copy the file ImPNM.FileType.dll to the Paint.NET\FileTypes\ folder Remove other plugins supporting the same file types (.pam, .pbm, .pgm, .ppm) from Paint.NET\FileTypes\ folder (to avoid possible conflicts) I.e. 'PNMPlugin.dll' plugin. After a restart of Paint.NET you will find the plugin in the 'Save as type' selector of the 'Save' and 'Save As' dialog. 'Load' does not use a dialog. Compatibility Paint.NET 3.5.11 and 4.0.5 Supported languages English Dialog options Save as .PAM dialog options Output color model selector You may choose between: RGB+Alpha, RGB, Gray+Alpha, Gray, Black and White + Alpha, and Black and White. Because the internal color model of Paint.NET is RGB+Alpha the plugin has to convert the existing image data if you are choosing a different output model. RGB+Alpha: Outputs RGB + A. RGB: Blends the image against the background color (w/o effect if the image is opaque). Outputs RGB. Gray+Alpha: Calculates gray values from RGB values. Outputs G + A. Gray: Blends the image against the background color (w/o effect if the image is opaque) and calculates gray values from the resulting RGB values. Outputs G. Black and White + Alpha: Calculates gray values from RGB values. Converts Gray to BW. Outputs BW + A. Black and White: Blends the image against the background color (w/o effect if the image is opaque) and calculates gray values from the resulting RGB values. Converts Gray values to BW values. Outputs BW. 'Maximum value in channel' numeric control In Paint.NET the maximum value in all channels (R, G, B, and A) is 255. This control allows you to use any value between 1 and 65535. The formula to map the channel values is dstValue = (srcValue * maxValue + 127) / 255 For sure if you are scaling the value up then you will not get more details in the picture. No magic. The maximum value used by 'Black and White' is always 1. Background color selector This color is used if one of the color models w/o alpha is selected. Save as .PBM, .PGM, and .PPM dialog options There is only one difference against the .PAM dialog. Instead of the color model (which is fix by the file type) you are able to select between a raw (binary) and a plain (Ascii text) mode. Known issues The color wheel control used to set the background color does not match the size available in the dialog. It looks somehow OK in Paint.NET 3.5.11 but not quite good in Paint.NET 4.0 BETA. Maybe this will change in a later version of Paint.NET. To Do list Optimize for speed Examples Paint.NET forum logo in PAM format.zip History 1.1 (19.2.2015) Fixes the issue that the plugin opens the web page of the plugin w/o a request of the user. 1.0 (27.2.2014) First public release

Compared to 3.5.11 the colorwheel in 4.0 is not packed to the limited size in the save dialog. But the readonly state of the colorwheel is much better in 4.0.

Just a small warning. I installed the update and tried to test if the switch between GPUs works better (Issue mentioned in the Glass border thread). This killed the system somehow. In the moment I'm just able to use this W7 laptop in safemode because atikmpag.sys crashes even if the driver is disabled.