Problem with image loading in the future?

[Slim]

The other day I discovered that a one of my devices with Windows CE.NET 4.2 didn't have the "imgdecmp.dll". Guess that the OEM didn't include it but then I read an article about it.

"Imgdecmp.dll will be removed from a future version of the Windows Mobile platform."
http://msdn.microsoft.com/library/defau ... rs_faq.asp

Maybe I was unlucky this time, but what if "imgdecmp.dll" is becoming more and more unusual? What will happen with the image loading in PocketFrog?

"SHLoadImageFile" in "aygshell.h" can't be a good solution since it's only available for PocketPC devices and not for the ones with WindowsCE. Will the "imaging.h", mentioned in the msdn-link, become the solution?

Regards

[muff]

yes, in Windows Mobile 5 they have knackered imgdecmp.dll (or at least it's likely to fail with current hacks)

but the replacement code is not that difficult and there is a sample in the new SDK's that means it can be up and running pretty quickly (I got it up and running in less than an hour in my non-PF environment)

so I dont think that patching a fix into PF will take long

[oliverzy]

yes, I have encountered this problem in my new Windows Mobile 2005.At first I thought PocketHAL doesn't support Mobile 2005, at last I found the DecompressImage function cause a infinite loop when it load image.Now I use SHLoadImageFile to replace it,it works well.

[muff]

SHLoadImageFile only loads certain formats

but essentially it's quite easy to add support for image loading in WM5 without the VOImage hack to use imgdecmp.dll

[Birdiestyle]

Has anyone implemented this in PF the right way
(detect and only use on wm2005) yet and care to share?

Is this the only problem with PF/PH on WM2005, this seems to blow it up, but once you get past this, does the input stuff and everything seem to work correctly....

Thanks

[Presto]

I'd be interested in hearing a solution too... Since the pre-2003(?) OS doesn't have SHLoadImageFile and the new 2005 OS doesn't have imgdecmp.dll, has anyone tweaked PF to load using one or the other, based on what's available?

-John

[muff]

personally I created a separate code path for each OS (switches based on defines) and compile for each OS separately - not ideal, but works

and there are loads of other things to be aware of that are WM5 only, hires support, screen rotation etc - so for me it made sense to create separate codepaths and compile for each OS separately