Rick Brewster

If possible don't use TIF. Paint.NET's support for TIF is basic and "best faith effort" only. It's only included because GDI+ already has a codec for it. I recommend using PNG instead. Also I'm not sure what you mean by "Photoshop-style alpha channel." Paint.NET images always have an alpha channel since 32-bit RGBA is the only pixel format that it used internally. However, an alpha mask is not natively supported, which would essentially provide a 2nd alpha channel for a layer.

The error code in the log is 0x88985003. After some digging, that is the DirectWrite error code for File Not Found. I suspect you have a font that is incorrectly installed or has been deleted improperly (I'm not sure how/why). It's probably whichever font you're trying to use with the text tool.

I have had other reports of this. It seems to happen when Paint.NET v3.5+ is installed or updated while a not-up-to-date Visual Studio 2008 is open. To help prevent this, I highly recommend enabling Microsoft Update. This option is available within the Windows Update application, and expands the updater to cover all other Microsoft software you have installed (not just the OS). It's very handy!

Nobody said you couldn't. Nobody said I couldn't, either, although you do seem to be looking for an excuse at machismo. There is more to adding a feature than just the lines of code you barf out in a weekend that implement it. Simplicity and complexity, in software development anyway, is hardly a one-dimensional property. Oh snap, indeed. user banned

And don't assume the presence or lack of a feature has anything to do with "difficulty."

What pyrochild said. Try asking your laptop manufacturer?

I e-mailed with one of the developers on DirectWrite about this. The hypothesis is that the font cache was corrupted somehow due to an improper shutdown (or something). This was causing the font cache service to reject the invalid font cache file (those .dat files you deleted) and rebuild it every time. Deleting the font cache file, as you did, fixes this. This is slightly speculative since we don't have access to your system, of course. Anyway they're aware of the issue now, if they weren't already.

This certainly will not be added to any v3.5.x release. The reason is that v3.5.x is in "maintenance mode" so that I can focus on v4.0 development. "Maintenance mode" means that updates are released only for bug fixing and maybe performance improvements. Nothing can be added which would require a localization pass (any new translation), which means no new features. (They'll be put into v4.0 instead.)

GIF usually has very low quality and should only be used in specific situations.

The "..." is for any menu command that requires additional user input to complete. Originally I thought it was for any menu item that would result in a modal dialog, but I was wrong. Hence why (IIRC) older versions of Paint.NET have a "..." for Help->About but more recent ones do not.

It's standard Windows UI guidelines. I don't know why you're assuming it was a "spontaneous design decision" from "back in the early days". You're weird man. Stop posting when you're drunk.

No, that's a bad idea. Then it would be doing all sorts of CPU and disk grinding even if you weren't going to use the Text tool.

Whoever said anything about a "production environment" ?

Ok, seriously Oliver? This thread is 5 years old. The original post isn't even here. (got deleted in some guests-can-no-longer-post migration) Make sure you read the rules before posting again. Thread Closed

You say this is after "initial launch". Initial after what? Startup / reboot? Paint.NET on Win7 uses DirectWrite, which does have a font cache of some kind that it builds the first time it is used in a session. You can set it to auto-start from the Services management console. (Although I recommend using "auto (delay start)".) It's simply called "Windows Font Cache Service."

Sidescroll wheel support is not available in current releases of Paint.NET. I plan to add this for the v4.0 release.

That rule doesn't exist. The layer name gets copied to the clipboard because, for some reason, that's what the Windows Vista+ text label control does when you double click it. Won't be an issue in PDN v4+.

It's a very low priority.

Then either use a mutex, or use a local variable to create the dictionary and then assign it to the static field as the very last step.

Paint.NET only works with 32-bit images that are 8-bits per color and alpha component. 48-bit images will be truncated to 24-bit, and then given an opaque alpha channel. No plugin can possibly change this.

if (plgLang == null) throw new ApplicationException("Call init plz. Kthx."); Or you could just call Init() for them, and make Init() a private method.

Those strings are there. Nothing is missing in the download.

How else would they be translated? Magically? I'm not sure what else you're looking for here.

I've edited the thread title so that it isn't in ALL CAPITALS SHOUTINESS. Please don't do that.

Paint.NET cannot be controlled using the command line like that. Also, version 3.31 is EXTREMELY old. Get the latest version already! Seriously, why people don't install updates is so far beyond me that it completely blows my mind into itty bitty pieces that even a microscope can't find.