Rick Brewster

Does not repro.

Yikes. There's really no way to tell what state your system is in at this point ... sorry but I have no idea other than what's already in the big sticky'd post in this section.

Or you can use the mouse wheel.

As an update to this, I have a fix ready for v3.5.2. Paint.NET v3.5.2 will now use GDI to get the list of fonts. This will give it the "expanded" list of names, e.g. Arial, Arial Narrow, Arial Black. It will then ask DirectWrite to create the font, and if that fails it will roundtrip the font through CreateFontFromLOGFONT(). This will then give it the correct Family Name + Weight/Style/Stretch that DirectWrite expects. In other words, it will convert "Arial Narrow" to "Arial" + Stretch=Narrow. This will all happen behind-the-scenes, so you won't have to worry about any of this. Also, bitmap fonts such as Terminal, System, and Courier will now be available as well. DirectWrite doesn't handle these types of fonts, but GDI does. So, Paint.NET will now detect DW's refusal and use GDI as a fallback.

Moved to Troubleshooting

4 processor sockets, or just a regular quad core CPU? In any case it doesn't matter, of course Paint.NET will work. It's been optimized for it since v1.0 in 2004.

Works just fine here. You're the only one who's reported this.

Clearly this is not a Paint.NET issue. Please go ask the tablet manufacturer. Thread Closed

Who knows .... why do you keep asking so many questions? :?

For some reason, it looks like you don't have .NET 3.0 installed (yes, .NET 3.0). I've seen this in some crash logs that've been sent to me. I've not been able to reproduce this myself, but you'll have to find some way to completely repair / reinstall / fix .NET. Start by getting rid of .NET 3.5 SP1, then try and fix .NET 3.0 (I don't know how), then install .NET 3.5 SP1 / Paint.NET 3.5.1.

Oh my gosh you guys, this is the dumbest thread all week. If you don't like System Restore, then TURN IT OFF. Saying things like "Paint.NET forces me to do a restore point..." to make it sound like you're being oppressed is just silly and lame. Thread Closed (btw do not PM me about this. seriously ... if a thread is closed then it's closed.)

4.0 will run on nothing less than Windows 8 with 2gb RAM and psychic powers. In all seriousness, I would not count on XP support for 4.0. In reality, I have not yet decided.

This is Word's thing. Right click the image -> More Layout Options -> Size. (at least that's in Word 2010)

Reinstall "Microsoft .NET Framework." You need version 3.5 SP1. http://www.microsoft.com/downloads/deta ... da479ab0d7

Moved to Troubleshooting

Looks like I've got a fix that I can put in for v3.5.2. DirectWrite lets you control the rendering mode as well as the measuring mode. The bug here is that the renderin mode was "aliased" and the measuring mode was using sub-pixel precision instead of pixel-snapping precision.

There's really no sense asking when Paint.NET v.Whatever is going to be out. You'll know it's coming when there's an alpha or beta.

No, we will not be putting up a link to Paint.NET v1.0. Thanks for the sentiment though.

No. It hasn't even been started.

Sorry, no, and the rules prohibit this. Thread Closed

The FileType class gives you a Stream because it expects you to use only that for saving/loading. What you need for icon saving/loading is the ability to open multiple workspaces associated with the same filename and save command, and to be able to group them together (logically and visually). Paint.NET just isn't made for that.

Yeah SuperSampling only works for reduction.

Ok seriously, I said we need to get back on-topic instead of keeping this as a soapbox about "why I think the latest Paint.NET should be / should not be / should / should not / Rick's wrong / Rick's right / you're wrong / I'm right". It's all extremely repetetive and completely anti-productive. I made many judgement calls during the development of v3.5 but I didn't keep a diary about every single one of them. You just have to trust that I made an appropriate decision that didn't just take your specific needs/opinions/wants in mind. Thread Closed

I'm sure it's possible but we don't provide support for anything but the latest version of Paint.NET. Sorry. Thread Closed

Yes, we know the bug still exists.