Jump to content

midora

Members
  • Posts

    1,782
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by midora

  1. 13 hours ago, Peter1 said:

    There is only one, named ImZIP.FileType, and it does not save the current PDN into a zip, which I would need. It puts the layers as individual graphics +metadata into the zip (which is riskier than a PDN.zip. I would even have to find out which layers graphics format is original PDN, is it ARGB?)

    That's exactly what a .pdn files contains. All layers and the layer attributes (plus a preview image needed for thumbnail in Explorer).

    Why would you be interested in the internal format if you just use it as backup. The important thing is that you can restore your pdn work at any time.

    Just save as zip and load it back.

     

  2. That's a limitation of paint.net. If there is built-in .jxl support for still images you need an alternative extension to open animated variants.

    That's the reason why there are plugins for .agif, .apng, .awebp (and in the future .aavif and .ajxl).

    A solution would be that the built-ins detect that the file contains an animation, cancels the loading, and ask paint.net to use a filetype variant which supports animations.

    Anyway it will take a while until all browsers support animated avif or jxl (Chrome supports animated avif but that's it).

  3. 1 hour ago, otuncelli said:

    Paint.NET shows an error if user cancels the dialog. Some people think it is an actual error. Maybe upcoming Paint.NET v4.4 will fix this problem.

     

    The ImPDF plugin throws an OperationCanceledException in the case that the user cancels the load dialog. I proposed to handle this exception silently a while ago.

     

    Stupid cat, take the chair 😉

  4. PDN3 files contain serialized .NET code.

    I guess the switch to .NET5/.NET6 changed something there.

    The deserializer in this plugin is not based on any .NET libraries. It's pure C code.

    I'm wondering that it worked for so long. 😉

     

    You may check what's happening loading the file with a paint.net release < 4.3 of paint.net or maybe add such a file zipped so if someone is interested and has enough time can have a look to the differences.

  5. I just figured out there is already a WarningException in c#. (You never stop learning 😉 )

    I will replace the exceptions in the code which just provide informations to the user (like that webp can only handle a maximum image size of 16383x16383) with this WarningException. This has no immediate effect but maybe Rick could handle them a little bit different in the future.

    • Upvote 1
  6. Hi @Pixey that's an error message of the built-in webp filetype plugin (located in the Bundled folder of paint.net).

    You have to change the extension of the file to .awebp (or to disable the built-in).

     

    It would be good if paint.net would allow a WarningException which just shows an information message and not this general error message with the embedded exception stacktrace.

     

     

  7. Release 1.4 [2022-01-24]
    - Fixed a bug in TransitionFade in case the final frame is transparent
    - Remove duplicates from frames is now always true and disabled because the
      WebPEndoder will do this in all cases.

     

    Sorry to update this plugin a second time in a week but I discovered a quite old bug in transition fade doing the transition example above. The same issue exists in ImAGIF.FileType but I do not expect that someone will use fading against a fully transparent background if the file format only supports 1-bit transparency. So this bug will be fixed there together with other improvements.

     

  8. The following image demonstrates that WebP animations support 8-bit transparency (compared to the 1-bit transparency of GIF animations):

     

    2022-01-24-Web-PLogo-Transitions.webp

    This animation has been created using the following layers and transition commands defined in the layer names.

     

    2022-01-24-Web-PLogo-Transitions-Layers-

    The animation starts with the layer at the bottom.

    Each layer will be shown for 2000 ms.

    After this time the layer uses a transition method to skip to the next layer.

    The transition method creates 20 layers in 1000 ms.

     

     

    • Upvote 1
    • You're a Smart Cookie! 2
    • Hooray 1
  9. Release 1.3 [2022-01-20]
    - Updated to use libwebp 1.2.2 (x64, x86) (contains the bug fix for progress values > 100%)
      There is still the libwebp issue that the progress reporting in the lossless case is limited

     

    BTW: Since a month or so there is no longer an issue on my side regarding the forum software. Upload of files and responding to topics works smoothly. 🙂

    • Like 2
  10. The progress handler allows paint.net to throw the OperationCanceledException (if SupportsCancellation is set). This may be important to allow a fluid change of parameters by the user if the save operation is slow and/or the image is quite large. So you should not suppress progress calls.

     

    I'm happy that the progress parameter is not an int. This allows to show a higher granulation without an interface change.

     

  11. Hi @gizzer. Typically you are using layers to do this.

    - Create a new image (which starts with one layer).

    - Paste the background image to this layer

    - Open the layers window and add a new layer. This layer will be the selected layer.

    - Paste your icon to this layer. (You may skip the previous step because you can paste to a new layer)

    - Flatten the limage. Means the layers are merged to one single layer.

    - Save the result.

    The flatten step may not be required because image formats like png or jpeg will do this for you on save.

×
×
  • Create New...