+1 800 256 3608 (toll-free in North America) or +49 7531 90 60 10| service@combit.com

Bitmap & DBF Memo for L & L


(Guest) #1

hi,

what Type of DBF Memo, with Bitmap inside, can be used
with List & Label 13 ?

with Xbase++ i can use different Memo Field setting e.g
Sixdrive, Comix etc.

i can include “external” Bitmaps in L & L Designer and
i do have my Memo Field too , but Preview/Print are
empty !?

so it might be that my DBESYS setting for Memo Field
is not what L & L “recognize” as Bitmap ?

greetings by OHR
Jimmy


(Guest) #2

This is not possible directly. You need to create a bitmap from that
BLOB (either save as temp file or create a bitmap in memory) and pass
the resulting filename (as path) or handle (LlDefineFieldExtHandle())
to LL.

How the BLOB represents the whole bitmap data is unknown (it’s a BLOB
;-)), and how you need to create a bitmap from it, this is something
you must know anyhow.

Paulchen

so it might be that my DBESYS setting for Memo Field
is not what L & L “recognize” as Bitmap ?


(Guest) #3

hi,

This is not possible directly. You need to create a bitmap from that
BLOB (either save as temp file or create a bitmap in memory) and pass
the resulting filename (as path) or handle (LlDefineFieldExtHandle())
to LL.

How the BLOB represents the whole bitmap data is unknown (it’s a BLOB
;-)), and how you need to create a bitmap from it, this is something
you must know anyhow.

thx for Answer. Now i get it work but with bad result.

the Bitmap is “crop” @left Side and that “crop” is going to right side …
i did send a Msg and Picture from that BUG to your Support.

After long Discussion in Alaska Forum it seems that List & Label
can not be used with Memo BLOB “direct” without that BUG. It
do work with “external” Bitmap but this is not a Option for me.

greetings by OHR
Jimmy


(Guest) #4

forgot :

L & L 13 without Servie Pack -> No Display
with Service Pack -> Display with Error

greetings by OHR
Jimmy


(Guest) #5

Well, they got several SPs :wink:

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


(Guest) #6

hi,

know what the contents of the BLOB are?

that is exact the Reason i ask how L&L is expecting
Bitmaps store into Memo. There are different Way !!!

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.

false. Read in Alaska Forum

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.

hm … but Xbase++ do not have a “Handle” and it seems not possible
to get a “Bitmap Handle” from a Xbase++ XbpBitmap Object ?

so back to my Question : how must a “external” Bitmap store into a
Xbase++ Memo “internal” to be used with LlDefineFieldExt() direct ?
( i guess L&L can use BLOB direct if it have the right Format ? )

greetings by OHR
Jimmy


(Guest) #7

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.

false. Read in Alaska Forum

I won’t. It’s cold enough already here. :wink:

But I know enough of bitmap formats to repeat: it’s impossible to
decide the color depth of a picture reliably, given only the picture’s
data. Especially when it’s not known whether the data contains header
information and such.

hm … but Xbase++ do not have a “Handle” and it seems not possible
to get a “Bitmap Handle” from a Xbase++ XbpBitmap Object ?

This is beyond my knowledge, but XBase++ users or developers should
know how to create a picture (whatever format) from a BLOB that the
user stores in a database. I repeat: a BLOB is just a collection of
bytes. What makes it useful is that you as developer should know what
type of information they represent.

so back to my Question : how must a “external” Bitmap store into a
Xbase++ Memo “internal” to be used with LlDefineFieldExt() direct ?
( i guess L&L can use BLOB direct if it have the right Format ? )

In any format L&L supports. BMP, TIF, JPEG, whatever. Nobody can tell
unless he has the internal knowledge about BLOB data.

Its’ like a (opaque) bag with some pieces in it. Could be anything,
even nothing. You ask me now how I could create a specific castle from
these parts. But there are different castles, and I do not know what
kind of pieces are in the bag - could be a Carrera racing track or a
Lego starship. I wouldn’t know. The only persons that know that a
castle could be built, and how it can be done, are either you (who
knows what kind of data the BLOBs contain - you did store it there!)
or the XBase++ developers, which built in special knowledge about the
data into this special BLOB in order to be converted back using the
correct transformation (if needed).

If you store pictures in it, store the files’ bytes, and revert that
process into a temporary directory while printing. No problem. If this
is a security risk (and you did not answer my question inhowfar this
is one), you need to know how to create a handle from the data - read
MSDN or Feng Yuan’s book on how to create a DIBSection or a DIB from
any data. How to do that in XBase++ is unkown to me, as XBase++ is
from a foreign planet as far as I’m concerned, and as I don’t know
what kind of pieces are in the BLOB bag, i.e. what format the stored
data is in.

Paulchen


(Guest) #8

hi,

false. Read in Alaska Forum

I won’t. It’s cold enough already here. :wink:

haha very funny …

But I know enough of bitmap formats to repeat: it’s impossible to
decide the color depth of a picture reliably, given only the picture’s
data. Especially when it’s not known whether the data contains header
information and such.

So all People in Alaska Forum are stupid ? Include Till (from Alsaka) ?

hm … but Xbase++ do not have a “Handle” and it seems not possible
to get a “Bitmap Handle” from a Xbase++ XbpBitmap Object ?

This is beyond my knowledge, but XBase++ users or developers should

this is what i say. List & Label did NOT respect Alaska Xbase++ Memo
Format like C:\ALASKA\XPPW32\SOURCE\samples\DATA\BMPDB.DBF

so back to my Question : how must a “external” Bitmap store into a
Xbase++ Memo “internal” to be used with LlDefineFieldExt() direct ?
( i guess L&L can use BLOB direct if it have the right Format ? )

In any format L&L supports. BMP, TIF, JPEG, whatever. Nobody can tell
unless he has the internal knowledge about BLOB data.

please read my Question carefull !

i do not ask what Picture Format, i do ask how L & L wanted to have
those Picture Format store into Xbase Memo File in which Format ?

greetings by OHR
Jimmy