Rick Brewster

Administrators
  • Content Count

    16,504
  • Joined

  • Last visited

  • Days Won

    154

Everything posted by Rick Brewster

  1. You can install this build which has @null54's fix for this: https://www.getpaint.net/files/zip/test/paint.net.4.212.7448.30753.install.zip (The only difference between 4.2.11 and this 4.2.12 build is the fix for this issue.)
  2. Why would you want to type text that isn't visible ... ? The canvas scrolls to ensure the text cursor is still visible. Unless you're seeing some other kind of weird/buggy behavior ...
  3. I'm sorry you're stuck on XP for now but we have a hard policy against providing any support or download links for older versions. Your best bet is to just do a Google search for version 3.5.11.
  4. Yeah this is just something I missed. I can make sure it's in there for the next update. Thanks! Microsoft may even have an official version of this, which I would use. There's usually not a need for translators to provide this image.
  5. Windows XP hasn't been supported for a very long time. Paint.NET will not work on it. Also, you should not use Windows XP for anything -- it's no longer supported by Microsoft in any way. That means no security updates, which means it's at risk of being targeted and infected. It's just a bad OS to be using in 2020. Don't do it. If you obtained Paint.NET from the Microsoft Store, be aware that the Store is only for Windows 10. It doesn't exist on previous versions of Windows. You'll need Windows 7 SP1 or newer to install the "Classic" edition of Paint.NET.
  6. That's never fun to figure out 😬 Good luck!
  7. Locking this thread -- Final build inbound. Also, there was a memory leak that I fixed for the final release.
  8. Locking this thread -- new update inbound! update:
  9. This update adds XMP metadata support, 3 new translations, some UI improvements, and several bug fixes. I'd like to point out the addition of a right-click menu that's now available from the thumbnail strip at the top of the window: If you’re using the Windows Store release, you should get the update automatically within the next 24 hours. You can also force an update check by following these instructions. For the Classic release, you should be offered the update automatically within the next week or so. You can get the update sooner by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website. Changes since 4.2.10: New: XMP metadata is now preserved for supported file types (PDN, JPEG, PNG, TIFF, JPEG XR, HEIC, AVIF, WEBP) New: Belarusian (be) translation New: Greek (el) translation New: Slovenian (sl) translation New: Added a right-click context menu to the image thumbnail/tab. It contains commands for Copy Path, Open Containing Folder, Save, Save As, and Close. New: The items in the File -> Open Recent menu now have a tooltip with the full file path for the image Changed: The selection outline animation is now smoother (2x the framerate) Fixed: Saving with the HEIC file type is no longer limited to a max Quality value of 90. This limitation was in place because of a crash due to heap corruption, which no longer happens. Fixed: The NVIDIA sharpening setting will no longer cause trippy distortions in the canvas area Fixed an issue with loading very small TGA images, first reported here: https://forums.getpaint.net/topic/116100-tga-rle-truecolor-1x1-image-failed-to-load/. Thanks @null54 or the fix! Fixed: Error dialogs when opening images now consistently show the file path Fixed a PropertyNotFoundException error message when saving JPEG images with a particular ordering of metadata. This was due to a bug in Windows 7's WIC JPEG codec. First reported here: https://forums.getpaint.net/topic/116079-jpg-cant-save-some-file/ Fixed clipped text rendering in the Curves adjustment dialog in some non-English translations. Fixed a crash when running the app with a DPI scaling setting of 500% Fixed a crash that would sometimes happen when running effects with very small selections Fixed some IndirectUI controls not honoring their default values if also initialized in read only (disabled) mode. Thanks @BoltBait for the fix! Fixed a memory leak in the effect system that was causing 1 orphaned thread per effect invocation Changed: Removed the use of NTFS Transactions, which was causing trouble with OneDrive. Microsoft has also deprecated this technology. New: Added /openCrashLogFolder command-line argument. This is intended for simplifying troubleshooting workflows. New: Added /forceUpdateCheck command-line argument. This is intended for troubleshooting scenarios to simplify acquiring the latest version, e.g. "just run paintdotnet:/forceUpdateCheck" instead giving a longer list of buttons to click on. Updated WebPFileType plugin to version 1.3.4.0, which adds XMP metadata support. Thanks @null54! Updated DDSFileTypePlus plugin to version 1.10.3. This fixes an issue with saving in the A1R5G5B5, A4R4G4B4, and R5G6B5 formats, and adds support for reading files that use a 'BC7\0' FourCC. Thanks @null54! Enjoy!
  10. Your .NET Framework installation still seems to be corrupted or broken somehow. Paint.NET is crashing hard when trying to initialize WPF. Either that or you have some other software on your system that is trying to inject itself into other processes, and it's causing the problem. Common examples of this include various security software, WindowBlinds or other theming hacks, GPU monitoring/overclocking software, multimonitor management software (like NVIDIA nView).
  11. Okay, the new 4.2.11 beta build 7441 has NTFS Transactions completely disabled. No need for /disableNtfsTx from here on out.
  12. Well, armed with that information, there's a good chance I'll just make it the default (to disable NTFS Transactions, that is) So if you get an error message when trying to use the /disableNtfsTx command-line argument, just remove it.
  13. New build posted, closing this thread
  14. NOTE: This was originally posted as build 7440, but has since been updated to build 7441. This new beta build just fixes a few small things since the previous one (build 7433). We're almost ready for the final release To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app). You can also download this build directly: https://www.getpaint.net/files/zip/test/paint.net.4.211.7441.385.install.zip Changes since 4.2.11 beta build 7433: Fixed: "Open Containing Folder" now selects the item in the Explorer window Fixed: Saving with the HEIC file type is no longer limited to a max Quality value of 90. This limitation was in place because of a crash due to heap corruption, which no longer happens. Fixed a bug where the selection would disappear forever if the canvas was scrolled away from it Fixed errors when trying to save into certain cloud-sync'd folders, e.g. OneDrive for Business. This was done by disabling the use of NTFS Transactions. Enjoy!
  15. I don't think it's a bug in Paint.NET. You're the only one reporting this problem. Just because you have an SSD doesn't mean paging isn't the problem. SSDs are a lot faster than HDDs but they're still immensely slower than regular RAM. That's why paging is always bad. Just because you have 5GB "free" and you're opening a "small" image, doesn't mean memory isn't an issue. JPEGs in particular can decompress to very large amounts of RAM. It will depend a lot on the size of the images you're working with -- the size in pixels that is. You have to look in Task Manager to see how much memory Paint.NET is using. Don't just look at "Memory (active private working set)", but add the column called "Commit Size". That tells you how much total memory each process has allocated, not just how much is resident in physical memory.
  16. There's no trick, the clipboard is just a cranky thing in Windows, to hand-wave a summarization of the many long battles I've had with it. Also, you didn't specify which version of Word you're using ... make sure you're using the latest. Same for Paint.NET.
  17. Yes, here's a direct download link for this build: https://www.getpaint.net/files/zip/test/paint.net.4.211.7433.39692.install.zip Are you using a proxy on your network? Those don't work well with the updater
  18. This is absolutely happening -- I've got working code for that now! I actually just forgot to implement it. It was on the list. I had way too many windows and tabs open, and it just got lost in the scroll. Thanks for the reminder
  19. The alpha went quite well -- there were just a bug that popped up in the UI code for the updater that seems to be finally squashed for good now. So, here's the beta! There are a few more fixes and improvements, most notably a right-click context menu has been added to the image/tab's thumbnail. You can also open up this menu by pressing Alt and - (minus). To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app). Changes since 4.2.11 alpha build 7420: New: Added a right-click context menu to the image thumbnail/tab. It contains commands for Copy Path, Open Containing Folder, Save, Save As, and Close. New: Slovenian (sl) translation New: Added /forceUpdateCheck command-line argument. This is intended for troubleshooting scenarios to simplify acquiring the latest version, e.g. "just run paintdotnet:/forceUpdateCheck" instead of a list of buttons to click on. New: Added /disableNtfsTx to disable the use of NTFS Transactions when saving images, which affords troubleshooting some scenarios that may be problematic. New: The items in the File -> Open Recent menu now have a tooltip with the full file path for the image Fixed: Error dialogs when opening images now consistently show the file path Fixed a crash that would sometimes happen when running effects with very small selections Updated WebPFileType plugin to version 1.3.4.0 (thanks @null54!) Enjoy!
  20. If it's a "low end" laptop then maybe you just don't have enough RAM for the images that you're trying to work with. Virtual memory paging could definitely cause 10-30 second hiccups.
  21. You install it from within the Microsoft Store app that comes with Windows 10. That should be all you need to do.
  22. You already got your answer, @Muntz. Stop dumping on all the other threads you can find on this issue. This is your only warning.