Fix for Non-Working Thumbnails of .PDN files (red x icon)

[casbreuk]

For the first time EVAR on any of my computers, I've managed to get the thumbnails for .pdn files to display!

OS:  Win7 x64

Paint.NET v3.5.5 (Final Release build 3.55.3767.28608)

I've always only seen the red x icon for the .pdn files.

Since win7 doesn't have a File Types tab in the folder options anymore, I used a program called:  "FileTypesMan"

I was just trying to get windows to show the PaintDotNet icon from its exe, instead of the ugly red x.

Even if I changed the icon and hit refresh, the red x would appear again.  Made me think it was actually attempting to display a thumbnail, but didn't know how.

So, I changed the File Type to DOCUMENT (was IMAGE).

Poof!  Suddenly, the thumbnail properly appeared!

So, I think you guys have a bug in the thumbnail code...

Edited September 25, 2010 by casbreuk

[Rick Brewster]

Doesn't work here. Good try though.

I've had a bug filed on this for awhile.

[csm725]

Works for me on Home Prem. Thanks very much!!! Highly appreciated.

[Rick Brewster]

Hmm, well it doesn't work for me. Too bad, I really want to know why this happens. Especially why it only happens on some systems but not others.

[csm725]

What view are you in in Explorer when you're looking at the pdn files? (just checking )

[Rick Brewster]

Thumbnails.

[csm725]

Like this, right?

Works for me on single- and multi-layered pdn files. Could that be an issue?

[Rick Brewster]

That's the view I'm using.

[csm725]

Thought so. Did you run FileTypesMan as admin when changing the type of the .pdn file?

[Rick Brewster]

Looks like I finally figured this out. It seems that the DirectX SDK litters some generic thumbnail handler all over the place, and one of the registry keys is uses has a higher precedence than what Paint.NET has been using.

If you go to the following registry key:

HKEY_CLASSES_ROOT \ Paint.NET.1 \ ShellEx \ {BB2E617C-0920-11d1-9A0B-00C04FC2D6C1}

and change the (Default) value to:

{D292F82A-50BE-4351-96CC-E86F3F8049DA}

(the old value may have been "{8938a035-768d-40c5-9560-bb901087e2af}")

Then this will fix it. I'll see if I can get a fix in place for the v3.5.6 release.