dzImage Library

[agraham]

I get the same on my Axim X30. It seems that not all devices appear to support saving anything other than BMPs even though the MS documentation for the Compact Framework implies that they should. However SaveImageBMP should work.

[klaus]

Hi Andrew,
You are right, SaveImageBMP does work.
I have modified the test code for the three image formats.

Best regards
Klaus
Switzerland

[brathbone]

Hi agraham,

Thank you very much for posting the BitmapStreamSaver! I'll just need to add a fallback to BMP for incompatible devices. For thos devices that are compatible, this will be a big performance boost.

It's almost for me.

I have successfully used the following code from the Desktop IDE v6.05, but I cannot compile. The compiler shows error CS1026: ) Expected on the following line:

bitmapstreamsaver.SaveImageToStream(mystream.New2( client2.GetStream,0), mybitmap.Value,"J")

I suspect it is because I am calling mystream.new2 (I tried New1 as well) in the SaveImageToStream call. I tried creating the stream and just handing it to the SaveImageToStream call, as below:

(This code compiles, but does not actually function. When I run the compiled executable, it complains that Stream2 was not assigned any value)

mystream.New2(client2.GetStream,0)
bitmapstreamsaver.SaveImageToStream(mystream, mybitmap.Value,"J")

Any ideas as to where my syntax has gone wrong? Here is a more complete example sequence:

dzImageclass.ScreenCapture
mybitmap.New3(dzImageclass.Image)
bitmapstreamsaver.SaveImageToStream(mystream.New2( client2.GetStream,0), mybitmap.Value,"J")

As a side note, the unoptimized compiler will compile this code, but the compiled app does not send image data on desktop and complains on the device about an optionally assembly that cannot be found.


Thanks very much for all the help so far. It is truly appreciated.

[agraham]

I don't know what sort of object "my stream is" but I think it is unnecessary, just pass the stream from your client to the function.

bitmapstreamsaver.SaveImageToStream(client2.GetStream,mybitmap.Value,"J")

"New" methods don't generally return anything so are not valid as parameters in calls to Subs.

[agraham]

Originally Posted by brathbone

complains on the device about an optionally assembly that cannot be found.

This an error, the missing assembly contains complete error messages, caused by another error that therefore cannot be displayed. The missing assembly is sometimes not installed to save space. See here error messages on device

[brathbone]

Huge thanks to agraham!



Sorry it took me so long to respond; my workload got the best of me.

I now have a (mostly) working remote control agent for PPC. It looks like the Treo 750 is one of those devices that doesn't natively support saving to JPEG. Fortunately I was able to fall back on BMP.

I sincerely appreciate the time and effort of everyone who responded to my questions.

Have a great weekend,

[agraham]

Originally Posted by brathbone

It looks like the Treo 750 is one of those devices that doesn't natively support saving to JPEG. Fortunately I was able to fall back on BMP.

I have since found an authoritative quote from Microsoft that only WM5.0 and later support saving other formats than BMP. The OS DLL in WM2003 can apparently do it but the OS code to exploit it was omitted for some reason.

[klaus]

In using sahoopes CapSure Screenshot program I noticed a strange behaviour with the saved bitmaps.
Saved with the SaveImageBMP routine of the dzImage library.

As shown in the picture below, the original file Wine1dz.bmp is displayed upside down with ACDSee thumbnails, but it's normal in the viewer.

The vaHelpMaker doesn't recognize this file.

I copied it into Paint, selected the whole image and saved it back under Wine1.bmp and this file is OK.

I compared both files with Total Commander, and
- the bitmap width F0 00 00 00 (240 pixels) is OK
- the height 40 01 00 00 (320 pixels) is OK in the Wine1.bmp file
- but in the Wine1dz.bmp file it looks strange C0 FE FF FF (complementary value) ?

Has anybody experienced the same problem, or is it also due to WM 2003 as for saving jpg and gif format which do not work either?

Included the zip file with the 2 bmp files.

Thanks in advance.

[agraham]

Originally Posted by klaus

or is it also due to WM 2003 as for saving jpg and gif format which do not work either?

Nothing to do with that, that was an omission. Bitmaps in files can be saved top down or bottom up, normally bottom up. Wikipedia - "Uncompressed Windows bitmaps can also be stored from the top row to the bottom, if the image height value is negative". It looks like for some reason the Compact Framework saves bmps top down - I have no idea why! Apps may or may not interpet this correctly if they don't expect negative values.

[klaus]

Hi agraham,
Thank you for the explanations, now I understand better what's behind.
I was not aware that bitmaps could also be saved top down with a negative height value.

Best regards