Rick Brewster

The other type of curve that our Line/Curve tool supports is just a simple spline. Basically it ensures that the curve always goes through each control point (nub), whereas bezier curves have different properties.

Hahahahaha that cracks me up. It's my new wallpaper.

You have to install the East Asian language files. Control Panel -> Regional and Language Options -> Language tab -> "Install files for East Asian languages"

You can already do this.

Courtesy of Wikipedia, here's all you need to know about Bézier cuves : http://en.wikipedia.org/wiki/B%C3%A9zier_curve (waits for heads to explode.....) Basically it's a way to draw a curved line based on where you put 4 points.

I'm not sure why they archive all those beta releases, since they've all expired by now ... weird.

Thanks, I've updated the language pack download thread (http://paintdotnet.12.forumer.com/viewtopic.php?p=1970)

Actually that's just some random truck in the background, it's no H2.

points to new sig Ok ok this one has a BMW in it, ya happy?

What is a "tech brush" ? Paint.NET v2.61 doesn't support user brushes anyway though.

I don't think there is such a thing as Visual Studio 2005 "Standard". I doubt the Express editions will cut it.

Well, while waiting for the download to start working, might I suggest these to pass the time ... http://www.c895fm.com -- The Vortex is on until 2am http://www.deviantart.com/view/30962827/ -- Cool wallpaper http://larenn.deviantart.com/ -- Cool artist

Hmm, the download isn't working for me. It keeps timing out or something. Yay for savefile.com?

That's pretty much how it always works out, BuzzKill (Consider we had 200,000 downloads in March -- yet look at how relatively inactive the forum is in comparison)

Here's another thing I'd like you to try. 1. Run the setup program. Wait until you get that arcane registry error dialog box like what you have above. 2. Go to Start->Run, then type "cmd" in the text box there and click OK. This will bring up the good ol' NT command prompt. 3. Type the following: (I recommend copy+pasting this) "%WINDIR%\Microsoft.NET\Framework\v2.0.50727\caspol" -rsp "%TEMP%\PdnSetup\SetupFrontEnd.exe" Note: This assumes you are not on a 64-bit system (99% likely). 4. Either copy+paste the results or post a screenshot. Mine prints the following, for reference: Microsoft (R) .NET Framework CasPol 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. Resolving permissions for level = Enterprise Resolving permissions for level = Machine Resolving permissions for level = User Grant = version="1" Unrestricted="true"/> Success

If the registry key doesn't exist, it will be created. That would not crash Paint.NET. I'm still trying to figure out what is causing this error, so maybe you could answer the following really quick: 1. Are you running as an Administrator user? (we're only supposed to let you do the updates if you are ... so if it's letting you install anyway then that's no good) 2. If you delete the registry key, HKEY_LOCAL_MACHINE \ SOFTWARE \ Paint.NET, and then try again, does it work? 3. If #2 doesn't work then please do the following for me: a) In Registry Editor, go to HKEY_LOCAL_MACHINE \ SOFTWARE, and right click on it and then click "Permissions..." The top list box will show various users or user groups. The bottom list will show what permissions they have for that registry key. Can you detail what all these are? For example, on my system I get: Administrators have Full Control, and Read CREATER OWNER has Special Permissions (greyed but enabled check box) Power Users have Read, and Special Permissions (greyed but enabled) SYSTEM has Full Control, and Read Users have Read If there are any checkboxes in the "Deny" column, be sure to list those as well. 4) Do the same as #3, except for the HKEY_LOCAL_MACHINE \ SOFTWARE \ Paint.NET key (assuming you tried to install and got the same "permission denied" error and have not deleted the key again in the meantime)

Our uninstall requires .NET as well. You'll need to have .NET 2.0 installed in order to uninstall Paint.NET v2.61 correctly. Otherwise you'll just be hacking away at the registry, which is generally not a good idea.

We do not provide 2.5 for download anymore.

Yup, it's C#. You'll find good reference for the Math functions here, btw (it uses the .NET Framework stuff): http://msdn2.microsoft.com/en-us/library/system.math(VS.80).aspx That URL doesn't seem to get linked up correctly with this forum software. D'oh. Copy and paste wins this round. Also, I recommend setting the language filter to just C#)[/url]

No sorry, this isn't possible with our toolset. While it's true that the eraser simply works on the alpha channel, we don't have a tool for setting the alpha channel to 255. Although a CodeLab script to do this is trivial: void Render(Surface dst, Surface src, Rectangle rect) { for(int y = rect.Top; y { for (int x = rect.Left; x { ColorBgra c = src[x, y]; c.A = 255; dst[x, y] = c; } } } I drew some red brush strokes, erased it all with the Eraser tool, and then this script "restored" the stuff I'd just "hidden."

Nobody's saying or implying this. Don't assume that either. Please don't lash out because Paint.NET doesn't work on your computer. Paint.NET was downloaded over 200,000 times during the month of March alone, during which we did almost a full terabyte of website traffic even with most of our downloads being handled by BetaNews. The total download count since October 2004 (when we started keeping stats) is quickly approaching 2 million. This is not to compare "sizes" (so to speak) but leads in to the next statements... The number of bug and crash reports I get is very small in proportion to those numbers listed above. The vast, vast majority of users have absolutely no problem installing and using Paint.NET. I'm not stating this to single you out and say we think your computer is "below the minimum requirements." Nor is it an implication that we think you're incompetent, stupid, have "done something wrong," etc. It is just a fact that it is impossible to write client software that runs on everybody's system correctly. If it wasn't your system, it would be someone else's. I could ramble for at least a full hour about all the various little (and big) changes that have been made in the name of compatibility. For instance, we used to use the Windows Scripting Host (WSH) during our installation process for a few purposes; it let us write something like "CreateDesktopShortcut()" in about 5 lines of code. But people reported crashes in our setup program, and for the life of me I couldn't figure out. Finally I figured out that sometimes anti-virus software is configured to block WSH completely, with the rationale that it can be used for malicious purposes (which I disagree with: are shoes illegal because they can be used as blunt weapons?). So I had to write a few hundred lines of C#->COM interop and go straight to the shell interfaces. But hey, it solved a huge compatibility problem for us. And it's only natural that a forum named "Bugs & Troubleshooting" would have large number of threads related to bugs and troubleshooting. There have been bugs reported in the past that did affect a large number of users and, thanks to the users who reported them and engaged in a dialogue with us, we were able to fix them for all users. We are still in that process with the registry permission issue you saw. Your statements there is akin to walking to the "Returns" line at a department store, seeing 3 people in line, and stating "Everybody I've seen is returning what they bought here! There is something radically wrong with this place." Well what do you expect, you're in the Returns line ... I, for one, have seen a steady drop in the rate of postings in this section of the forum over the last few months. Like I said, the vast majority of users have no trouble at all with Paint.NET. However, for those that do have trouble, I ask that they send a crash log, bug report, or engage in some kind of dialogue to help us figure out and solve the problem. You've done this for us, so thanks for that much. Unfortunately I just don't have a solution for you at this time.

Since v2.5 we finally have the rendering framework necessary to do something like this. Now we just need a good management framework for this kind of stuff, at which point this is something we can do. So, as usual, the answer is something like "everything in good time, please don't hold your breath because there's barely 2 developers working on this in their spare time".

Nope. We've exhausted everything I know of to try and fix this problem. I cannot help you further. Sorry it doesn't work on your computer.

This is not the thread to post in for suggestions. Just create a new thread. No reason to keep this thread open any longer, it's just causing confusion on where people should post. (so I've locked it)

There's a bug in GDI+ with respect to loading DPI from non-JPG images. It does not work. Therefore, it does not work in Paint.NET. We have a bug on this. If you want to preserve DPI you will need to use JPG or PDN for the time being.