Jump to content

otuncelli

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by otuncelli

  1. It was previously passing all tests on VeraPDF conformance test. But I checked again, It seems to fail on one now. Do you know any other conformance tests? Edit: Fixed the issue. Embedding layer/document properties won't break anything anymore. It passes conformance tests and Adobe Reader can open it.
  2. @lynxster4 Thanks for testing. Tbh, I've never tried opening with Adobe Reader. I'll look into it. I'm getting the same error. Edit: Turns out Adobe Reader doesn't like the way I embed PDN's layer & document configuration into the PDF. Foxit Reader and Mozilla don't have a problem with it though. I'll add an option to disable this. Edit 2: The option is added. Disabled by default. Edit 3: Fixed the main issue. Embedding layer and document configuration shouldn't cause any trouble now. The option is set to enabled again by default.
  3. I'd like to get feedback from experienced users before I release this. Import interface: Some features: PDF Import/Export with same plugin. GhostScript is not required. Based on current latest Chromium/PDFium. Supports importing Adobe® Illustrator® Artwork (.ai) files saved with PDF compatibility option. (Experimental) Has support for importing password protected PDFs. Saving protected PDFs is not supported (yet?). Has native ARM64 support but I couldn't test this because I don't have a compatible device. Can embed layer and document configuration into PDF as marked object data. When you import that PDF again, those configuration will be restored. But this is an alpha release and things may change. Also Adobe Reader seems to have issue opening those PDFs. Supports exporting in PDF/A-1b and PDF/A-2b standards. Export/Save functionality can be disabled by creating an empty file named PdfFileType.DisableSave.txt in installation directory and restart Paint.NET. This will prevent accidental overwriting if you're worrying about this. Adobe® Illustrator® Artwork (.ai) import functionality can be disabled by creating an empty file named PdfFileType.DisableAi.txt in installation directory. Has support for embedding layers as lossy (as JPEG) or lossless format. Has 4 modes for exporting: Normal: Each layer as page. Cropped: Bounding transparent pixels in each layer will be detected and removed automatically. So, in resulting PDF, each page can be different size. Cumulative: Each layer blends over the previous one using the selected blend option for that layer. Page 1 = Layer 0 Page 2 = Layer 0 + 1 ... Page n = Layer 0 + 1 + ... + n- The idea is from this topic: Flattened: Single page, flattened image. Has option to skip invisible or duplicate (containing same pixel data) layers when exporting. Allows importing all pages, certain pages, or same pages over and over again as different layers. Known Issues: Can't process very large images. (width x height x 4 > 2.147.483.647) For exported PDFs, only first page will contain the document configuration (Dpu and Dpu Type). If you don't import first page, this configuration won't be restored. Preview generation is not supported. Installation: Note: Before install please make sure you don't have any other file type plugin installed handling the same file types as this plugin. Download and extract PdfFileTypePlugin.zip If you're using Paint.NET 4.3 or later: If you're using Classic version of Paint.NET: Create a new folder named PdfFileTypePlugin in the <Paint.NET>\FileTypes directory (default location is C:\Program Files\paint.net\FileTypes). If you're using Microsoft Store version of Paint.NET: Create a new folder named PdfFileTypePlugin in the <Documents>\paint.net App Files\FileTypes directory. Put the extracted files in this newly created folder. If you're using Paint.NET 4.2: If you're using Classic version of Paint.NET: Put the extracted files in the <Paint.NET>\FileTypes directory (default location is C:\Program Files\paint.net\FileTypes). If you're using Microsoft Store version of Paint.NET: Put the extracted files in the <Documents>\paint.net App Files\FileTypes directory. Optional: If you want to disable Save PDF functionality, create an empty text file named PdfFileType.DisableSave.txt in the same directory. If you want to disable Adobe® Illustrator® Artwork (.ai) support, create an empty text file named PdfFileType.DisableAi.txt in the same directory. Restart Paint.NET. Download Link
  4. Select the transparent pixels with Magic Wand tool. Apply Edit->Invert Selection (CTRL+I) Apply Image->Crop to Selection (CTRL+Shift+X)
  5. Each plugin that uses OBL should contain their own specific version of it, not necessarily the latest one. PDF File Type's Open variant also contains a copy of it. Save variant doesn't. You can get it from here: If everything goes as planned, I'll release an alternative PDF/AI File Type plugin soon which doesn't require GhostScript nor OptionBasedLibrary. It'll also have native ARM64 support.
  6. First one is by a mistake which will be fixed in the next version of Paint.NET I assume. C:\Program Files\Paint.NET\FileTypes\SvgFileType.dll, version 1.0.0.0 Type: System.Web.IHttpAsyncHandler System.TypeLoadException: Could not load type 'System.Web.IHttpAsyncHandler' from assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. For the second one, update to latest version of SvgFileType plugin. There was ASP.NET dependency in SVG.NET library for some reason.
  7. @null54 ILSpy shows me that you're using 4.2.16 libraries for references. This is not a good idea. It'll mostly work but things (methods and stuff) you're using may not be available anymore or their behaviour may be different for some reason. I'd suggest referencing PDN 4.3's libraries to minimize the risk. This is WebP plugin. Same for AvifFileType and DDSFileTypePlus. // Detected TargetFramework-Id: .NETCoreApp,Version=v5.0 // Detected RuntimePack: Microsoft.NETCore.App // Referenced assemblies (in metadata order): // PaintDotNet.Base, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null // Assembly reference loading information: // There were some problems during assembly reference load, see below for more information! // Error: Could not find reference: PaintDotNet.Base, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null // PaintDotNet.Core, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null // Assembly reference loading information: // There were some problems during assembly reference load, see below for more information! // Error: Could not find reference: PaintDotNet.Core, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null // PaintDotNet.Data, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null // Assembly reference loading information: // There were some problems during assembly reference load, see below for more information! // Error: Could not find reference: PaintDotNet.Data, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null // System.Collections, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // System.ComponentModel, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // System.Drawing.Common, Version=5.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (unresolved) // System.Drawing.Primitives, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // System.Linq, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // System.Runtime, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // System.Runtime.InteropServices, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // System.Runtime.InteropServices.RuntimeInformation, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved) // WebP_ARM64.dll // contains no metadata // WebP_x64.dll // contains no metadata // WebP_x86.dll // contains no metadata For my plugins, I'm doing it like this in project file. This resolves version conflicts and also helps me to see which things are available (or not) in each version of PDN. Unfortunately I couldn't find an official way to acquire older versions of PDN libraries for backward compatible development purposes. I took a backup before installing 4.3. <ItemGroup Condition="'$(TargetFramework)'=='net47'"> <Reference Include="PaintDotNet.Base"> <HintPath>..\4.2.16 Libs\PaintDotNet.Base.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Core"> <HintPath>..\4.2.16 Libs\PaintDotNet.Core.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Data"> <HintPath>..\4.2.16 Libs\PaintDotNet.Data.dll</HintPath> </Reference> </ItemGroup> <ItemGroup Condition="'$(TargetFramework)'=='net5.0-windows'"> <Reference Include="PaintDotNet.Base"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Base.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Core"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Core.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Data"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Data.dll</HintPath> </Reference> </ItemGroup>
  8. I've just checked this on my friend's Windows 10 build 1607 and it shows correctly. Chrome still shows the same brighter colors which has nothing to do with WIC. Something might be broken on my Windows then. I'll check this. Edit: It turns out my default device profile has been changed to something I don't recognize. Switched back to sRGB and it shows correctly now.
  9. My File Explorer shows like the first image but desktop thumbnail shows like the second image. If I increase the thumbnail size one tick it turns to first one. I'm on Windows 10 LTSC 1809 with latest updates installed. Middle image is the correct one. Which Windows build version are you using? @midora
  10. Not respecting the embedded color profile can be problematic in some very rare cases. The test image taken from here: https://www.donationcoder.com/forum/index.php?topic=9529.0 I also tried this image with Windows 98's pbrush.exe and it shows the correct colors 😆 Something must have been gone very wrong with WIC. I wonder why.
  11. Updated to v1.04. Changelog: Fixed a size detection problem. Added support for rendering use element when importing with layers (experimental) Fixed a crash when clicking the GitHub link on Paint.NET 4.3+ License changed to LGPL
  12. What happens if the plugin both supports load and save with custom loading UI? (which I'll probably release soon.) I'm already using IsReflexive => false though using a stopwatch to catch chained OnSaveT=>OnLoad calls. Instead, I'm showing a message to user that informs about preview generation is not supported by the plugin. protected override Document OnLoad(Stream input) { return stopwatch != null && stopwatch.ElapsedMilliseconds < 100 ? GetPreviewNotSupportedDocument() : new MyFileTypeImporter().Import(input); // <-- this opens loading interface } protected override void OnSaveT(Document input, Stream output, PropertyBasedSaveConfigToken token, Surface scratchSurface, ProgressEventHandler progressCallback) { // First call is always for preview generation :) if (stopwatch == null) { stopwatch = Stopwatch.StartNew(); return; } // DoSomething stopwatch = Stopwatch.StartNew(); } But I can't prevent OnSaveT running after first call. Stream type checking or using reflection (StackFrame to check caller method's name which contains 'Preview' if its for preview generation) break the rules. I can't use these. I think the decision of preview generation should be given to the developer. Not all formats are save/load fast or resource-friendly.
  13. Probably because it overrides IsReflexive => true. Because it's a lossless filetype plugin. AFAIK Paint.NET doesn't call OnLoad method to generate preview in this case. No problem. I'm kinda new
  14. No Here is the screenshot with Photoshop plugin. It's not a plugin issue.
  15. It happens with other layer supported filetype plugins too. I've just checked Photoshop plugin. It looks like a Paint.NET issue. It also might be intended for memory-usage concerns.
  16. I was using the portable version (paint.net.4.300.7894.40357.portable.x64.scd.aot.zip). Now installed and it's working fine.
  17. Current alpha (7894.40357) can't load plugins from <Documents>\paint.net App Files. Is this intended? I know this directory for the store version' plugins but it was working with regular Paint.NET 4.2.16 too.
  18. Hi @ThreadSnake This could be related to an issue with SVG.NET library internally used by the plugin which does the actual SVG reading. Issue is here: https://github.com/svg-net/SVG/issues/837 I'll check this again more thoroughly. If it's something I can fix, I'll update the plugin. Viewbox and Viewport fields are just informational fields. You can't edit them. Thanks for reporting. As a workaround, adding "viewBox" attribute to svg definition seems to fix the problem. <svg xmlns="http://www.w3.org/2000/svg" width="500" height="500" viewBox="0 0 500 500">
  19. You're using the other SVG import plugin. I'm getting the same error message when i try to use the other one. Seems like it hasn't been updated for a long time so i would expect it to fail on .NET 5. This one doesn't use OptionBasedLibrary and it's only a single file.
  20. Links updated to v1.03.1 🥰 Thanks to @AlexDolmatov and @AndrewDavid Changelog: Fixed a dependency loading problem.
  21. Links updated to v1.03 🥰 Changelog: Removed ASP.NET dependency of SVG.NET library.
  22. Updated to v1.02 🥰 Changelog: Fixed an error that causes paint.net to crash when setting canvas dimensions (#11) Updated to use SVG.NET v3.2.3 and Fizzler v1.3.0
  23. Updated to v1.01. Changelog: Fixed some bugs that leading crash. Some GUI changes. Viewport x, y values were not displaying correctly. Fixed duplicate import of groups when using Group import mode. Auto-generated layer names are now more meaningful. Added a memory warning message when importing many layers. Case-insensitive comparison of values for visibility attributes (visibility & display) for svg elements.
  24. This is a Paint.NET filetype plugin for loading SVG (Scalable Vector Graphics) and its compressed variant SVGZ files. SVG elements can be rendered as a flat image file or each on a separate layer. The plugin is a tiny wrapper around the SVG.NET Library which does the actual SVG reading. Tested on Paint.NET 4.2.16 & 4.3 Beta Build 7929. Download links Here are the download links for latest release: Installer Manual Installation SvgFileTypePlugin_setup.exe (399 KiB) SvgFileTypePlugin.zip (274 KiB) How to install 🔴 Note: Before install make sure you don't have any other file type plugin installed handling the same file types as this plugin. To auto install (recommended) the plugin perform the following steps: Download and run SvgFileTypePlugin_setup.exe Follow the steps of the setup wizard. To manually install the plugin perform the following steps: Download and extract SvgFileTypePlugin.zip If you're using Paint.NET 4.3 or later: If you're using Classic version of Paint.NET: Create a new folder named SvgFileTypePlugin in the <Paint.NET>\FileTypes directory (default location is C:\Program Files\paint.net\FileTypes). If you're using Microsoft Store version of Paint.NET: Create a new folder named SvgFileTypePlugin in the <Documents>\paint.net App Files\FileTypes directory. Put the extracted files in this newly created folder. If you're using Paint.NET 4.2: If you're using Classic version of Paint.NET: Put the extracted files in the <Paint.NET>\FileTypes directory (default location is C:\Program Files\paint.net\FileTypes). If you're using Microsoft Store version of Paint.NET: Put the extracted files in the <Documents>\paint.net App Files\FileTypes directory. Restart Paint.NET. Changelog and older versions can be found here. Source Code on GitHub
×
×
  • Create New...