Rick Brewster

Wow, the reference driver is slow.

No, you read it wrong. It's actually Doom and Wolfenstein 3D that he ported. This has nothing to do with Paint.NET, move along ...

You probably shouldn't be using Windows Server as a workstation. I recommend using Windows 7 instead.

Soap and water

Oh and I should add I'm planning to fix this for Paint.NET v4. This seems to be a bug in WinForms, so I just need to go direct to the Win32 API instead. Bit of trivia ... BMP bitmaps, which is what the clipboard uses by convention, are stored upside down*. You'll notice that at the bottom left of the image you pasted, there is a few pixels of giberrish. That's actually part of the BMP file format's header. * at least, upside down with respect to traditional "memory-correct" row ordering

Known issue.

A 1-bit image will expand to 32x its size when loaded in Paint.NET. And that's after decompression, mind you. The reason is that Paint.NET homogenizes all images to be 32-bit RGBA.

Lifehacker Pack 2010 - Our list of essential Windows downloads http://lifehacker.com/5548767/lifehacker-pack-2010-our-list-of-essential-windows-downloads "When you need to crop, cut, or otherwise edit an image, Windows' built-in Paint isn't quite enough, while a full-fledged Photoshop or GIMP installation is probably too much. Paint.NET is just about perfect for the graphic design needs of a non-graphic-designer."

How is this "slightly urgent" ?

Vista SP1 is a free download. Just go install it via Windows Update. There's really no excuse since it's been out for a few years, and ever superseded by SP2 now.

You can get it through Windows Update, too.

No permission to view topics. Looks like it needs a login.

That's because you're using an old version of the plugin. When something crashes, always always check to make sure you're using the latest version of anything.

You probably will want to use Edit -> Paste into New Layer instead.

Don't forget to search with http://searchpaint.net (also available from Help menu within PDN)

The clipboard is notoriously bad at preserving DPI. At one point (I think it was a year ago?) I tried to implement this so it would work as you expect, but it just refused to preserve the DPI metadata.

This is something that I was unable to fix for XP. Since 2003 is mostly the same as XP (at least for its File Open dialog, mind you), the issue persists there as well. This isn't an issue on Vista, Win7, or Server 2008 / 2008 R2. I highly recommend that you upgrade to Windows 7! Server isn't even meant for desktop / "workstation" use; it really is for server use, otherwise it's something of a misnomer. File associations are based on the file extension. Interesting maybe, but certainly not surprising

It's a command-line program. Hence the usage instructions talking about parameters, and not UI buttons.

Nope. That's a pretty niche feature.

It's a robot / spam forum. Linking to it will only encourage them Just click on the "Report Abuse" link at the bottom of the forum, and fill out the little form.

No it's not. It's a stance based on our right to minimize the amount of time we waste trying to help people who turn out to have older versions, on problems that are already fixed. I highly doubt that. Oh you mean other than to fix your computer? And your attitude? Take off your aluminum hat. SP3 for XP is free. Good luck with that. So? It's in Google Cache too, ya know. Stop trying to outsmart the Internet. Anyway, you're complaining and complaining and complaining about something I've given you for FREE. What a self-righteous, self-entitled attitude you have! Not even the briefest "thanks" before you launch into a tirade about how awful everything is and how right you are. You sir, are banned from this forum. Get out of here, you ungrateful snot.

You deleted registry keys? Oh boy. That won't help at all, and if Paint.NET is still installed it'll just make things worse.

You really should just run SFC instead of trying to outsmart a corrupted file. I'm not going to change the way I distribute Paint.NET because some people have run into trouble with corrupt files, failing hardware, and/or viruses. Best of luck fixing this.

I'm still not sure there's a bug, logically speaking anyway. Just because another program can't read a PNG created with Paint.NET doesn't mean that Paint.NET has a bug, mind you. For Paint.NET v4 I am going to be upgrading all the built-in codecs to use WIC instead of GDI+ so that should improve things. GDI+ is known to be bad in many, many ways -- including its codec implementations. In the meantime you haven't told us what version of Windows you're using or given us any means to reproduce the issue. That information will help And, you know, donations help motivation too. I can't do everything for free ya know.

Probably something like this. ColorBgra[] srcPixels = ... however you're getting this right now ... ; ColorBgra *pDstPixels = ... surface.GetPointAddress(roi.Left, roi.Top); fixed (ColorBgra *pSrcPixels = srcPixels) { IntPtr pDstPixels2 = (IntPtr)pDstPixels; IntPTr pSrcPixels2 = (IntPtr)pSrcPixels; ... now use either System.Runtime.InteropServices.Marshal.Copy() [i](which probably just calls into memcpy)[/i] ... ... or PaintDotNet.SystemLayer.Memory.Copy() [i](which definitely calls into memcpy which is optimized for SSE2 etc.) ...[/i] } Don't use the anything in the Memory class other than Copy and SetToZero, however. So, you can kick off all the rendering in OnSetRenderInfo(). Then, in OnRender() you wait for that specific region to finish rendering, then blit it to the buffer that DstArgs references.