Rick Brewster

Administrators
  • Content Count

    15,998
  • Joined

  • Last visited

  • Days Won

    126

Everything posted by Rick Brewster

  1. As @toe_head2001 alludes to, this is almost certainly caused by some other software on your system. Software like Window Blinds has been known to cause all sorts of trouble like this.
  2. Probably a bug in the plugin? ¯\_(ツ)_/¯
  3. This is fixed for the upcoming 4.2.1 release. Thanks for reporting it! The conversion from dpcm to dpi was being done wrong. It was dividing, instead of multiplying, by 2.54.
  4. Does this happen when saving any image? For instance, what happens if you start up Paint.NET and try to save the default/blank image? If that works, then maybe something's "bad" * in one of the images you're working on. If that's the case then it would help if you send me one of the images (just reply here and attach the image). * ("Bad" in the sense that Windows doesn't like it... not your fault!)
  5. Yup, by design. Otherwise you can never "hold on" to that original aspect ratio, it gets slushed away in rounding errors if nothing else. Your workaround is the right one, just "reset" the aspect ratio by bouncing it through the clipboard with Edit -> Copy Selection and Edit -> Paste Selection -> Replace.
  6. Yeah, that's clearly a bug. I'll see if I can get it fixed for the 4.2.1 update that's coming out very soon.
  7. Auto-detect will always include transparency if necessary, by way of choosing 32-bit. You'll only loose transparency if you selected 24-bit or 8-bit. (I think 8-bit also supports transparent, although not varying levels of transparency)
  8. I had temporarily deleted my reg key before I took that screenshot; it doesn't mean anything
  9. Also, if running as admin doesn't help (and for the record, that isn't meant to be a solution for you, but rather a debugging aid for me), try opening PowerShell and run this command: Get-Item -path HKCU:\SOFTWARE\Microsoft\Windows\DWM And see if there's a difference when running PowerShell normally, versus running PowerShell as admin. I get something like this: I don't think you'll see different values, but maybe you'll see an error.
  10. What happens if you... 1) Exit Paint.NET 2) Re-run it as Administrator? (right click on it -> Run as Administrator) and then: 3) Exit Paint.NET again 4) Run it normally?
  11. Can you send me the diagnostics info? Settings -> Diagnostics -> Copy to clipboard (button) Then paste the results here
  12. I fixed this already but thanks for reporting it
  13. Well, nothing changed in the app... this leads me to believe it's something on your end.
  14. Works totally fine here ... my settings are exactly the same as yours. ... Do you have Tablet Mode enabled or something?
  15. Show me your settings in Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM
  16. @zeromus Not a bug, and not due to any recent change. When you initially open an image, the Zoom is set to "Fit to Window". Panning isn't possible in that mode. You can toggle away from "Fit to Window" from the View menu, or by clicking the button at the bottom-right in the status bar (to the left of the zoom out button with the minus sign), or with Ctrl+B. This all assumes you have overscroll enabled (which is the default).
  17. Yesterday's build has a few things that I'm fixing in today's new build. Hopefully I can get the final build pushed out to everyone for this weekend! 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. Direct download link: https://www.getpaint.net/files/zip/test/paint.net.4.201.7152.40366.install.zip Changes since 4.2.1 beta build 7151: Fixed: JPEG XR support is limited to Windows 8 or newer (it doesn't work on Windows 7) Fixed: The old JPEG XR plugin is no longer blocked if you're using Windows 7 (btw it's actually more accurate to call it an HD Photo plugin) Fixed: The mouse wheel may now be used to scroll the Palettes menu in the Colors window (thanks @AndrewDavid for the suggestion and @toe_head2001 for the fix!) Changes since 4.2: New: JPEG XR file type support Fixed: Holding Ctrl when dragging a selection with Move Selected Pixels will again leave a copy behind (but only with the mouse) Fixed crashes when saving DDS images Fixed VTF plugin compatibility; it was not working in 4.2 except for images that were an exact power-of-2 size on each dimension Fixed: .BMP files can be opened even if they're not actually BMP images (they still need to be a valid WIC-supported file type such as PNG, JPEG, etc.) Fixed (stabilized) menu ordering of effect plugins that have duplicate names Fixed metadata handling that was preventing some images with EXIF tag 330 from being able to load Fixed metadata preservation for old images that pad EXIF string values with null terminators Fixed title bar text color when using certain custom accent colors in Windows 10 Fixed very bad performance when opening large images with embedded rotation metadata
  18. I'm putting up a new build in just a minute ... Closed
  19. For anyone else who's reading this: 4.2.1 fixes this. It was related to images with an embedded orientation tag. Like when you take a photograph in portrait mode. The same pixels are saved to disk as if you had taken it in landscape, but an extra EXIF metadata tag says "rotate the image by 90/180/270 degrees". However, the way Paint.NET was getting pixel data from WIC was not optimal, and it resulted in decoding the image over and over to get different regions of the image. A weird O(n^2) performance problem ...
  20. Pixels. Always pixels. You can't change it to something else.
  21. I'm going to adjust the block so that the old plugin isn't blocked on Win7.
  22. Okay it looks like JPEG XR requires Windows 8. I'll adjust the code for that.