Rick Brewster

Looks like another monthly release for Paint.NET is on the way! It's a minor update, although it has a new effect that has been requested many times (and that was also promise for v2.5 about a year ago ). Zoom Blur! This release will also fix the bug discussed over here: http://paintdotnet.12.forumer.com/viewtopic.php?t=1923 P.S. Anyone got a spare $50k U.S.? Those new 335's are hot ... hey a guy can dream :wink:

I've fixed this. It was a bug in GDI+'s Graphics.DrawImage() method. This fix will be part of the next Paint.NET update (v2.72) in early September.

.......... why? The tolerance is a 0 to 100% number, not 0 to 255. It isn't like the color values that are stored internally as a byte. I suppose I could make the top number be 7 or 893 or "elephant", too, if I really wanted :twisted:

I'd love to write a book, call it "Paint.NET Internals" or something. But ... with what time?

The tolerance control will be in the 2nd row of the toolbar when a tool that depends on it is active. It will also be larger to accomodate more precise configuration.

Paint.NET is not an animation program.

The French translation was updated last week for v2.70.

E-mail me one of the TIF files that causes the error and I'll check it out.

I don't know, you might be able to figure something out. It won't be quick or easy though.

You're right, that is off topic. Do a web search.

This has already been asked very recently. Please use the Search facility.

It's rude to bump a thread like that. If I wanted to update the FAQ, I would have by now. Locked

First, I have absolutely zero concern about pirated copies of Windows. Those people are on their own. Second, SP2 has been out for two years. That is plenty of time for people to have figured out how to get it on their systems. It is an important update that should be installed. Third, it is my opinion that not installing SP2 because of "DRM concerns" is a purely "tinfoil hat reason" (for the record I have not perused the EULA for this stuff -- I am not specifically familiar with what it says, DRM or not). Basically, the domain of conspiracy theorists and people who do not understand the technology. DRM is a tool for content publishers. If you don't like the terms of the DRM, then please don't purchase the content. The alternative to having a DRM framework in the OS is to have each content publisher try and cook up their own DRM system, and we all know how well that works (*cough* Sony *cough*).

No, sorry, I just don't have that information.

Older versions of Paint.NET are not available. http://windowsupdate.microsoft.com Install every update on there. Get a friend to help if necessary. "SP2" has many security-related upgrades and improvements; it's over 2 years old and very important, I'm very surprised that you don't have it already.

Ok, so go ahead and generate docs, I'm not stopping you Not all the code is documented.

This seems reasonable, and probably preferred behavior. The situations where a user would want to pick multiple colors is probably quite small, and even then there would be more clicking around and this would not add much of a burden (the scenario I'm thinking of is someone sampling many color values and then copy+pasting the hex codes into some HTML code or something). I've filed a bug to do this. The problem with doign something like this is that right now the code/logic for these tools is all separate. The Move tools share a bunch of code, and the Selection tools share code, but the two 'sets' of tools are separated. And the Move tools are actually extremely complicated. I was thinking about doing this, that is to say backporting it to the v2.xx codebase. It would have minor localization impact, but I just think it needs a more thorough test pass done on it. In other words, I'd like to see it go through the rigorous beta testing gauntlet that other releases have gone through. The reason v2.70 didn't really need a beta testing phase is because I just took a bunch of effects we already had lying around that had no bug reports on them, and integrated them into a well understood, stable code base. The new code for the Colors window is pretty solid, but I would not feel comfortable releasing it without all that testing and feedback first.

Reno, thanks. I've uploaded the update. By the way, the French language pack is very popular. It has been downloaded over 14,000 times just in August and accounts for almost 4% of our bandwidth usage. Just thought you might be interested in those numbers

There is no documentation. You will want to look through the code for examples.

Moved from Tutorials to General Discussion Like the forum states at the very top, it is reserved exclusively for tutorial publishing.

Because of our resource manager, the forms usually don't load up in Visual Studio at all. It throws a fit. But that's fine, we usually just edit the code manually. This has been covered in some other forum thread, I forget when though.

What are you even trying to do with the Paint.NET source code ... ?

Looks like Segoe UI. Maybe you installed the latest Office 2007 beta? Those fonts would have to be selected in the Display properties (in the Apperance tab, click "Advanced...") to be the default menu font. You might make sure that your Themes is setup right. That said, I've used Segoe UI with Paint.NET and it worked fine, so the font itself is not intrinsically "bad". The fault must lie elsewhere.

It's crashing while trying to get the default menu font. Maybe one of your fonts has become corrupt. It does actually happen ... I don't know why :\ Or, have you restarted recently, specifically since you installed the update? Yeah I know it's a copout but sometimes it does flush and fix things.

That restore window bug has been around for awhile. I can never seem to get a solid repro. It doesn't have anything to do with the mouse coordinate stuff.