Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by olavrb

  1. I use Paint.NET on multiple machines where I put app files (plugins) in my personal OneDrive, so I don't have to maintain this manually on all the devices.


    For machines without Known Folder Move (KFM) with OneDrive for Business, it has worked fine to create a directory symbolic link from "%USERPROFILE%\Documents\Paint.NET App Files" to "%ONEDRIVECONSUMER%\_Share\AppData\Paint.net\AppFiles", where I have the folders "Effects", "FileTypes" and "Shapes".

    • The "_Share" folder in my OneDrive is set to always be available offline, so no "Files on-deman" causing issues here.
    • Running v4.2.16 from Microsoft Store, but don't think that's relevant here.
    • Here is the CMD (as admin) command I used, if anyone is interested:
      mklink /D "%USERPROFILE%\Documents\Paint.NET App Files" "%ONEDRIVECONSUMER%\_Share\AppData\Paint.net\AppFiles"


    I think this failed this time due to my company using known folder move (KFM) with OneDrive for Business, as I see Paint.NET have created a "paint.net App Files" folder inside "%ONEDRIVECOMMERCIAL%\Documents". But symbolic linking from one OneDrive to another makes changes one place being uploaded to both OneDrives, so I'd rather avoid that if I could.


    Then I thought: It would be nice if it was possible to set a different directory for Paint.NET app files. Then I could just set this settings to the folder in my OneDrive.

  2. With Intune one have the option to package anything (EXE installer for instance) inside a "*.intunewin" package thanks to the "Microsoft Win32 Content Prep Tool" + Intune Win32.


    It would be awesome if the EXE installer "/auto" switch described here could be acompanied with a optional "/q" or "/quiet" switch which hides any GUI.


    This would make packaging Paint.NET to Intune even easier than it already is.

    • Currently one can "/createMSI" and put that directly to Intune or inside a "*.intunewin" package for more granular logic for detection and similar.
  3. I've bought the MS Store version earlier,

    but seeing how strong development still is for PDN, and that it's now being updated to .NET 5, I'm so stoked that I want to donate some more.


    Will donating from the PayPal phone (Android) app targeting donate@getpaint.net be any different than using the PayPal links at https://www.getpaint.net/donate.html? Regarding taxes and similar. Seems more convenient to use the phone app. 😊


  4. Decode support since v4.2.2 using Microsofts decoder from Microsoft Store is great, thanks for that. 😊 


    It would be even greater if Paint.NET could embrace this new open codec even further by implementing the ability to create lossy and lossless AVIF files. Not asking for an ETA or anything, but better get the discussion going sooner rather than later.


    Since it's about creating a single keyframe, visual quality should be more important than performance/ speed. Don't know enough about AV1 encoders to say which is most fit, but someone else might have the answer to that.


    Leaving some inspiration on the topic of AVIF:

  5. I don't own a ARM64 Windows 10 device yet, but if I ever got one I'd be very glad if Paint.NET could run natively on it.

    • Would it be possible to compile Paint.NET to ARM64 without too much hassle for you developers?


    Maybe release it in Microsoft Store only. I've already payed for the store version and I love it. I very much like auto updates + supporting the Paint.NET developers at the same time.

  6. 38 minutes ago, Lizasaur said:

    I opened up properties and you're right! It is a .webp

    Does that mean I can't open it? Or is there a trick to getting it to work?

    Thank you so much :D

    If it's a real WebP file you should be able to open it with Paint.net natively I think. You could also try to install this extension for Windows 10, it lets you open WebP files natively in the "Photos" app:

    If it's not real WebP, maybe a PNG, remove the ".webp" in the end of the file name so it only says "<name>.png", then try open it with Paint.NET or Windows 10 built in "Photos" app.

  7. 3 hours ago, SodiumEnglish said:

    I don't think the video codecs would be relevant for an image editor. The image extensions you have listed would be the ones to use: HEIF, RAW, WebP.


    As for plugins already existing, there are already user-made plugins for RAW and WebP that you can use for both classic and Windows Store versions:

    Though, I have no idea how easy or possible it would be use those Windows Store items and could still be an option. However, how many image extensions are available in the store? If there are enough it may make sense to try and support them.

    HEIF image extension uses the HEVC video extension for the actual decoding. I think AV1 video decoder will be used for AVIF aswell. HEIF and AVIF are only containers, HEVC and AV1 are the format/ codec they use (yes, HEIF can take many other formats aswell).


    I also know of the user-made ones. But support for using Microsoft Store codecs for special image format decoding would be much easier to implement for users not that tech savvy. Plus "normal" users don't need to export to webp, avif and other fancy formats, they'll just be happy if they can open and edit photos from their phone and internet. I'm realising that I'm generalising much here, but yeah. :)

  8. Would be cool if both the exe installer version and the Microsoft Store version of Paint.NET could use the codecs available in the Microsoft Store to open special image file types. 

    This will mostly be decoding, AFAIK there is no encoder in these "codecs".


    Examples of codecs that would be relevant:

  9. First of all I'd like to say that I'm a long time user of Paint.NET, and just recently bought the Microsoft Store version. So far so good, well spent money.


    I'd like to request a feature addition: Ability to set a custom folder location for Paint.NET App Files.

    Today i use %userprofile%\Documents\Paint.NET App Files, symlinked to a OneDrive for Business folder, so I have the same tools across all my workstations.

    Have been working flawless until now, but symlinking is not compatible with OneDrive for Business latest features, "Known Folder Move".

    I'd like to have the ability in Paint.NET settings to set a custom App Files folder, directly to my OneDrive for Business folder.


    OD4B Known Folder Move - Paint.NET App Files symlink.PNG

  10. With Paint.net manual install version I could choose to open SVGs with Paint.net through the "Open with" dialog.

    With Paint.net Windows Store / UWP version, Paint.NET does not show as an alternative. I have to open Paint.NET first, then drag'n'drop a SVG on to it.


    I'm using this FileType plugin btw: https://github.com/otuncelli/Scalable-Vector-Graphics-Plugin-for-Paint.NET


    Is it possible to add SVG as a file type Paint.NET may be able to open, or is this a limitation with Windows Store/ UWP apps?

    Choosing the exe manually from UWP install folder (C:\Program Files\WindowsApps\dotPDNLLC.paint.net_4.101.6828.0_x64__h55e3w7q8jbva\PaintDotNet.exe) is not possible, gives an error code.

    Paint.net - SVG open with.PNG

  11. On 10/01/2018 at 7:01 PM, Rick Brewster said:

    Did you just recently turn on the "show accent colors on: title bars" setting in Windows? If so, this will likely go away the next time you ... I think it goes away when you restart, or logout/login, or maybe even just when you restart the app. (I forget which). This isn't actually a new bug.

    No, I did not recently turn on that setting. There have been several restarts of my Windows laptop since I reported this, and the issue is still present. 
    Also, it happens on both my laptops, so I think it's not a isolated case.

    Happens with v4.0.21 too (nothing regarding this in the changelog, but thought I should mention it)

  12. Hi!


    Let me start by saying that I LOVE the new black theme! :) But it has a little bug:


    When the Paint.NET window is not active, some places turn white. See this screenshot: 



    - This happens on both of my laptops, both running Windows 10 1709 16299.192 en_US. One 'Pro' and one 'Pro for Workstation'.

    - Happens both with theme set to auto, and dark.

    - Windows theme is set to dark.

    - Happens regardless of the "Show accent color on the following surfaces: Title bars" setting.

  • Create New...