Well, they got several SPs
Concerning your BLOBS: How should LL (or, to be fair, ANY program part
being passed a BLOB) know what the contents of the BLOB are? A BLOB is
defined by being just an array of bytes, without any connected meaning
outside the application’s code. Could be a sound, movie, random data
or a picture of one of the numerous formats.
So it’s in your responsibility to convert a BLOB to a data structure
that has some meaning known by standard software.
A BLOB is a black box. I could sell you one, telling you there’s some
mobility gear inside. Imagine you are blind (cannot distinguish the
devices easily): Do you know how how to handle a bicycle, a train, an
aeroplane, inline skaters, …, and would you detect any of these
correctly for use? Possibly it’s a nuclear submarine or a conventional
one (to be handled differently!), … It could be done to detect a
lot of the formats if you pass a pointer that INCLUDES the “magic”
identifier belonging to that format in the first bytes, but then
that’s not present not in all formats, and could cause all kinds of
GPFs.
Regarding a BMP, there are DIBs, DIBSections and BMPs, and all must be
created differently from a BLOB, which might be the file contents as
the BMP would be stored in a file, a BITMAPFILEHEADER followed by the
bits, or the colored picture bits (what color depth??? Impossible to
decide!). Indistinguishable automatically.
Long post, short solution: you need to create a picture in one of the
formats LL can use. Whether you do that in memory and pass the handle
to it (HBITMAP, HDIB, HENHMETAFILE) or as a file is up to you - but it
must be in the format defined by the type.
Paulchen
“AUGE_OHR” AUGE_OHR@WEB.DE wrote in message
news:49270192008201256@combit.net…
forgot :
L & L 13 without Servie Pack → No Display
with Service Pack → Display with Error
greetings by OHR
Jimmy