Rick Brewster

Ok I can reproduce this now. I've filed a bug. Thanks.

I can't reproduce this, nor have I received any other reports of it.

It will never happen.

You're not the only one in this predicament, ex. http://lifehacker.co...ould-be-on-macs The best recommendation I have is, honestly, to buy a copy of Parallels Desktop, http://www.parallels.com , and run Paint.NET in its emulated environment. They make it so that the Paint.NET window looks like an app that's running on your Mac desktop. Imagine taking a screenshot of your Mac desktop, then pasting in a screenshot of just Paint.NET, and there you go. Performance is good. It works pretty well and will also let you run any other Windows software that you may need or prefer to use.

Big mistake, unfortunately Always use the Add/Remove control panel. Use the Windows Installer Cleanup utility, mentioned in the big scary capitalized sticky post in this section of the forum.

I don't know why.

15 MP = slow. Simple as that.

Or at least a hammer and ... a small hammer.

Hmm, not sure what to tell you. I haven't seen any other reports of this. The MSI does work, promise! The MSI does install the required Visual C++ runtimes -- this is not something that the setup wizard does on the side, in other words. The ones used are from Visual C++ 2008 SP1, but they are not the version on Microsoft's download center. The one on the download center is actually old -- what you want is the "4148" version which has an important* security fix. Since you already have the 2008 SP1 "non-4148" runtimes installed, try this. Go to Windows Update and make sure you are opted-in to Microsoft Update. Then check for updates. This will make sure it catches updates for non-Windows, but still Microsoft, software. Paint.NET uses 3 parts of the runtime: CRT, ATL, and OpenMP. * In the grand scheme of things it's important (I think MS actually uses the term "critical"). However, I don't know if the changes affect Paint.NET.

That's because the extension method is being applied before the typecast operator is. (int)(some double expression).ExtensionMethod(); is equivalent to (int)((some double expression).ExtensionMethod()); Notice the placement of parenthesis.

This isn't a troubleshooting question, so I've moved it to General Discussion.

Ahh I must have changed the comment in the v4.0 code base then. The Utility class is being phased out, its functionality being moved into various *Util and *Extensions static classes. Extension methods are easy to use too. int x = ...; byte y = x.ClampToByte(); byte z = (int)(some expression).ClampToByte();

Is the obsolete attribute's message not showing up in CodeLab?

Paste into New Layer = your friend.

What I meant is that using the built-in updater is not supported after you've used the MSI. You must either install with the UI wizard, or the MSI, and can't use the other without uninstalling. You got the 1721 error on all systems or only a few? 1721 is a pretty generic error. Try looking at the log files in %TEMP%, such as PdnMsiInstall.log and PdnSetupNgenInstall.log.

Umm, guys, Utility.ClampToByte's obsolete tag also includes a message telling you precisely what to do instead. It says, "Use Int32Util.ClampToByte() instead." Ergo, my guess is that Int32Util.ClampToByte() might be useful.

Radial blur will probably be gated by memory performance. Even video cards have limits!

PdnRepair isn't going to do anything here, it isn't a magic cure all like that. It's only mean for installation-related issues. jonathonamber, when you merge two layers, you end up with 1 layer. That's the whole point of its functionality. Or are you saying that you have more than 2 layers, and after merging, only 1 layer in the entire image is left?

Use layers.

Unrelated and by design. It uses XOR and a stipple pattern. "Jagged" is really the wrong term here -- the selection's outline is anti-aliased, but purposefully textured.

10) "1603" error during install/update Loki has found what we believe is a fix for this, detailed at http://forums.getpaint.net/index.php?/topic/18931-fatal-installation-error-1603-fix/ SirHakon found another fix: http://forums.getpaint.net/index.php?/topic/30437-win7-error-1603-32-bit-msi-may-not-be-installed-on-64-bit-os/

More problems and fixes will be added as we find and collect them. Installation / Update problems Problem: There are many symptoms and causes. Solution: We have listed the solutions that we have found here: http://forums.getpai...tall-read-this/ Crashes with custom themes (WindowBlinds, uxtheme.dll patch) Problem: Custom themes and patched copies of uxtheme.dll have been known to cause many stability problems. Solution: If you experience crashes, try switching back to one of the themes that comes with Windows. Tip: If you have a crash log, you can easily tell if you're using a custom theme by looking at the "Theme:" information that's listed in the log file's header. In this example, the standard Windows "Aero" theme is being used. (This stability problem is one reason that, by default, Windows does not allow custom or "third party" themes!) Application version: Paint.NET v3.5.5 (Beta Release build 3.55.3762.38843) ... UI Theme: Aero/Aero + DWM (Aero.msstyles) Corrupt downloads - Alzip Problem: A zip program called "Alzip" has a long standing bug where it cannot open the the Paint.NET installer ZIP file. Solution: Don't use Alzip. Use WinZip, 7-zip, WinRAR, or even the functionality that's built-in to Windows itself. Various Plugin Problems Many plugin-related issues can be solved by reading this: http://forums.getpaint.net/index.php?/topic/9349-

The "dimensions" of the layer can simply be inferred by keeping track of the largest bounding rectangle around non-transparent pixels. No need to add clutter with a "resize layer" command.

If you really want, you can force any application to run with the Classic look. Right click on your Paint.NET shortcut, go to Properties, then Compatibility. Check the box that says "Disable visual themes" (and then click OK, of course). I've used this trick with the documentation viewer that came with Visual Studio 2008, because otherwise it had horrible flickering issues. Unfortunately, I just tried this with PDN and it doesn't seem to work ... YMMV, I guess.

One of the work items I have planned for PDN4 is to upgrade all the built-in codecs to use WIC instead of GDI+. (as another note, in Win7 the GDI+ codecs were actually rewritten as a layer on top of WIC!) That would improve things for JPEG, PNG, etc. As for supporting all the remaining codecs that WIC allows to be plugged in, I am also considering this but have not made a final decision. It will be a matter of scheduling and prioritization.