Jump to content

Rick Brewster

Administrator
  • Posts

    20,731
  • Joined

  • Last visited

  • Days Won

    386

Everything posted by Rick Brewster

  1. Works fine here. Press Refresh or clear your cache or something. And like it says above,
  2. As usual, you can either use the built-in updater from the Utilities menu, or you can download and install directly from the website: http://www.getpaint.net/ . There's no need to worry about removing the old version; that is all handled automatically. This update fixes several issues related to copy-paste, improves performance and quality for a few adjustments, and fixes a data loss bug. When pasting an image, Paint.NET will be smarter about ensuring it is placed within the area that has been scrolled/zoomed to. Improved the performance and quality of the Curves and Hue/Saturation adjustments. Some minor improvements to memory usage, which should help out a few scenarios on 32-bit systems. Fixed: If a JPEG was loaded that had an embedded ICC profile, and was then saved as an 8-bit or 24-bit PNG, then the resulting file would be corrupt (32-bit PNG worked fine though). Fixed: 16-bit TGAs no longer load with the red and blue channels swapped. Fixed: Copy-paste from a Remote Desktop session will no longer be 'shifted' by 3 pixels. Fixed: Copy-paste from Internet Explorer, Firefox, or Chrome should preserve alpha/transparency. Fixed: Copying from Paint.NET and pasting into Windows Live Writer should now work. Fixed: Taking a full-screen screenshot with Print Screen on a multimonitor system, where those monitors don't form a simple rectangle, will now fill the 'gap area' with transparent instead of black. (Example: two monitors of the same size, one of which is rotated by 90 degrees) Fixed: If Paint.NET is opened without specifying an image to open, and then the default image is modified and saved, then Paint.NET will no longer close it upon opening another one. This was causing data loss if that default image had layers, and was then saved in a format that did not support layers (anything other than .PDN). Fixed: Some systems were showing 'red X' thumbnails for .PDN files in Windows Explorer, instead of the real thumbnail. Fixed: The EXIF "Creation Software" saved along with images is no longer localized. This prevents certain languages from seeing "Paint.NET ????? v3.5.6" in the image properties (metadata). Hopefully these fixes should make the wait for 4.0 easier to bare Also, as a bonus feature which is a corollary to how I’m now handling copy-paste from Internet Explorer: if you “copy” an image from Windows Explorer, you can paste it straight into Paint.NET. For example, right click on some stray image you’ve left on your desktop (c’mon we all have a cluttered desktop). Next, paste into Paint.NET. Pretty cool, maybe even useful.
  3. .NET 3.5 SP1 is 100% required. If .NET 3.5 SP1 is not installed, or cannot be installed, then that's a huge problem. Paint.NET will absolutely not work. It does come with the installer, but it looks like that isn't working and that's where the problem is. .NET 4 won't be noticed by Paint.NET unless it's the only version of .NET installed. If you have any .NET 2.0 through 3.5, then it won't use 4.0.
  4. That's the thing ... on Win7 you shouldn't need to install .NET 3.5 SP1. It comes with the OS.
  5. Let me see if the merge thread thing works.Edit: It totally worked backwards. But I fixed it.
  6. Older versions are neither supported, nor provided. Please read the rules. Thread Closed
  7. Confirmed. As per the TGA spec, blue is in the low-order bits. Paint.NET was pulling blue from the high-order bits (and thus, red from the low-order bits). I'll have a fix for v3.5.6.
  8. I've found the problem. The image has an embedded ICC profile (EXIF tag ID #34675). When saving a PNG with this at anything other than 32-bit, this appears to be totally broken. I don't know if it's because GDI+ mangles it while saving, or if the PNG spec just says "if bpp isn't 32 and you have a 34675, then you are dead to me." This will be fixed in 3.5.6.
  9. I'm completely stumped as to why this was posted in Troubleshooting. Moved to General Discussions & Questions
  10. The size on paper is calculated from the pixel size and DPI. Not the other way around. Print Width = Pixel Width * DPI All you need to do is adjust DPI (resolution) until the print size matches what you want.
  11. This is an updated beta with a bunch more fixes and stuff. Head on over to the Preview Center section of the forum ...
  12. Ahh yes. There have been numerous reports of Visual Studio 2008 causing installation problems. Often this seems to happen if you have either not installed SP1 (for VS 2008), or if you don't have the absolutely latest updates for it. Enabling Microsoft Update from within Windows Update can help keep this automated and simple.
  13. 'amd64' just means x64 / 64-bit. It is named that because AMD had the 64-bit version of x86 CPUs first, and Microsoft needed a tag for it so they could add it to their builds. They also had x86 (normal 32-bit x86) and ia64 (Itanium 64-bit). Then Intel copied it for their CPUs too, and 'amd64' is something of an anachronism now. But it's still in use.
  14. What if you put the following at the beginning of your Paste() method, GC.Collect(); GC.WaitForPendingFinalizers(); GC.Collect(); GC.WaitForPendingFinalizers();
  15. It depends what thread causes the crash. In general it's a VERY VERY VERY BAD IDEA to try and do anything within Paint.NET at that time, even if the dialog is -- for whatever reason -- non-modal.
  16. This isn't a Paint.NET issue. And please, stop using IE6 already. Your time is more valuable than that (and so is ours).
  17. Why was this posted in Troubleshooting? Moved to General Discussion
  18. If you copy an image from Firefox, e.g. right click on any image and select Paste, then it only puts a CF_DIB on the clipboard. Paint.NET handles pasting this just fine. So, I do not know how to reproduce your specific issue with VMWare.
×
×
  • Create New...