Vector Class Map Macros

The bitmap and vector class map macros are provided to assist in connecting the different LEADTOOLS Class Library classes with classes you derive from LBitmap (see the Ltclibn.chm file), LVectorBase or LBitmapBase (see the Ltclibn.chm file). The mapped classes are created "on demand", that is, no class object will be created if you do not request that class object from the bitmap or vector object.

Connecting different LEADTOOLS Class Library classes to the bitmap or vector class object makes it easy to use these classes with the object when programming applications.

Every LEADTOOLS Class Library class you derive from these bitmap or vector classes must declare a class map. This is done through the LEAD_DECLARE_CLASS_MAP() macro in the header file that contains the declaration for the derived class. In the implementation file for that class the user must use the LEAD_START_CLASS_MAP(ClassName,ClassParent) , LEAD_INIT_…(ClassName) and LEAD_END_CLASS_MAP(ClassName,ClassParent) macros respectively.

Class maps completely support inheritance. If a mapped class is not found then the mapped class of the parent class will be used. Any inherited classes will use the newly mapped classes or the parent mapped classes if the child does not have a mapped class of the same type. This gives you flexibility in programming your applications while using different class maps for each derived bitmap class.

LEAD_DECLARE_CLASS_MAP

LEAD_START_CLASS_MAP

LEAD_END_CLASS_MAP

LEAD_INIT_xxxx

START_BITMAP_CHANGING

END_BITMAP_CHANGING

LDictionary_GetBitmapCount

LDictionary_GetBitmap

LDictionary_DisconnectBitmapList

LDictionary_IsBitmap