olavrb

I found here: That you can do Image -> Apply Embedded Color Profile, which makes the image look correct. So maybe not a bug/something that needs to be fixed after all. Maybe one could prompt the user to load the image with the color profile if a color profile is detected?

As a non-competent user I'd like to be able to open images in Paint.NET without colors looking funky by default. Thus I'd like Paint.NET to use the embedded ICC profile by default, either by: Load using ICC profile by default, or Prompt user to load image with the embedded ICC profile Paint.NET automatically detected. --- Original title: "PDN messes up colors on XYB JPG created by JPEG XL "jpegli", Windows Photos doesn't" Original content: After reading about JPEG XL "jpegli" I had to test it. Binaries can be found here: https://artifacts.lucaversari.it/libjxl/libjxl/latest/ Test image was taken from here: Web page containing multiple images: https://people.csail.mit.edu/ericchan/hdr/hdr-jxl.php Image in question: https://people.csail.mit.edu/ericchan/hdr/jxl_images/20140606_102418_IMGP0297.jxl Which I decoded to PNG using GIMP (opened in GIMP, chose to export to PNG). I then used following command to generate XYB JPG: cjpegli.exe .\in.png .\out-xyb.jpg --quality=90 --xyb --chroma_subsampling=444 And following for a non-XYB JPG: cjpegli.exe .\in.png .\out.jpg --quality=90 --chroma_subsampling=444 I then noticed that opening the XYB JPG file in Paint.NET messes up colors, while the Windows Photos app seems to handle it well. I don't know enough to tell what causes this. Color space? ICC? But if the Windows Photos app handles it, so should Paint.NET, ideally. Sample files (in.png, out.jpg, out-xyb.jpg) can be downloaded here (around 20MB): https://mega.nz/file/asAhyRqS#4iIzU4OoKc3SFzRB4h5018NOYfS5LKYfT9rPdbSxfIM

To add to what Rick said: Geek Uninstaller (free) can help to differentiate on Paint.NET installed through Microsoft Store vs. installed from EXE. https://geekuninstaller.com/download If the problem is to find out what version of Paint.NET to remove.

I looked for a zip, but should've "CTRL+F"-ed it. Thanks.

Feature request: Ability to select a different install directory. I sync Paint.NET App Files with OneDrive and use the registry keys for "Custom Plugin/Shapes Folders" ( https://www.getpaint.net/doc/latest/InstallPlugins.html ). Issue, or at least maybe something that can be made faster and more intuitive: Why loop through all the plugins at install when only a few are actually selected for install? It looks like the installer (v6.5) installs all the plugins (but it doesn't actually do that), even though I only selected one of them. So, misleading GUI IMO, and slow. Shouldn't the "Install selected" action detect enabled checkboxes and only loop through those? Also, the two errors when starting the installer when using the Microsoft Store version of Paint.NET could maybe be removed? Either try to detect whether Paint.NET is installed. PowerShell example: [bool]$(Try{$null = Get-AppxPackage -Name 'dotPDNLLC.paint.net' -ErrorAction 'SilentlyContinue'; $?}Catch{$false}) Or present a popup at startup "Regular installer or Microsoft Store"?

Thanks for this easy to understand tutorial on outlining text.

I'd like to learn why the Microsoft Store version of Paint.NET runs in the background? I'm not assuming anything bad, I'd just like to know what it does. This was after a boot, where I hadn't opened Paint.NET yet.

Plugin v1.0.8, PDN v4.3.11 from MS Store, Windows 10 x64, triggers prompt to install .NET Framework 3.5. Seems to be triggered by "RIOTProxy.exe". Expected? It's not mentioned in this thread or in the GitHub repo.

So, how long does it usually take before a new version of Paint.NET gets certified for the Microsoft Store? I've been checking for updates daily, also just now, but still stuck on v4.3.4.

Sorry for the very late reply. We're using Intune/ Endpoint Manager for the company I work at. There we publish apps in the Microsoft "Company Portal", so users without admin permissions (which should be all) can install optional software. One of those softwares in Paint.NET. Here, Microsoft Store (for business) is not feasible, as: We'd have to manually manage licenses. There is no such thing as a "pay as you go" model there AFAIK. It's being EOL-ed. Maybe we'll have a better replacement for it in the future? https://techcommunity.microsoft.com/t5/windows-it-pro-blog/evolving-the-microsoft-store-for-business-and-education/ba-p/2569423 https://docs.microsoft.com/en-us/lifecycle/announcements/microsoft-store-for-business-education-retiring The way we package apps is described in the first post. Why add totally silent EXE installer switch? Less manual steps to deploy new versions to Intune, as we don't need to /createmsi first Would also make it easier to create logic for "auto updates" with some PowerShell. I'd prefer Microsoft Store version for this, but as mentioned, but how licenses in Microsoft Store for Business works is not feasible for us. BTW, I found that NSIS installer has a case sensitive switch "/S". This hides the first dialog, but after extraction Paint.NET dialogue appears. I've only tried this from user as admin context, will try to see what happens if deploying in SYSTEM context from Intune. Maybe it's not shown to the end user.

Ahh. That did it. Sweet. Thank you. Corrected PowerShell if anyone is interested.

@Rick Brewster Just saw 4.3 got installed through Microsoft Store today. Then had to check the forums. Then saw that you've implemented this feature request. Sweet. I then went ahead to try it. Made following PowerShell script: My "%OneDriveConsumer%\_Share\AppData\Paint.net\AppFiles" looks like attached picture. Inside there I have the MozJpeg plugins (https://github.com/0xC0000054/pdn-mozjpeg) amongst others. But I can't save to Mozjpeg. So don't think I've done it right. Settings don't mention any errors in "Plugin Errors". Except the already reported "PaintDotNet.Effects.dll. Do you see anything obious? I assume the name for each registry key is like you wrote it "Plugins/AdditionalPluginDirectoryRoots", with forward slash and all. For HKLM, you say true, registry don't have booleans, so I went with DWord. For HKCU, I have absolute path, as you can see from the screenshot.

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.

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.

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. 😊