Update Information for Version 16
The ListLabel class does have a new member "ProjectParameters" which enables
you to work with project parameters comfortably. Up to now that was only
possible with methods from the LlCore object.
The methods of the Dictionary property of the ListLabel component now have
overloads to support localization features. For the same reason there is a new
list of supported languages in the DesignerWorkspace class.
The Print and Design methods have new overloads that allow the stream-based
passing of project file and printer settings. This is particularly of interest if the
information is to be stored in a database.
Changes Compared to the Previous Version
The class PropertyFillingChart has been renamed to PropertyFillingWithBitmap
and inherits PropertyFillingExt.
The LlConst enumeration has been marked with the "Obsolete" attribute.
Generally all constants are already available in other enumerations. For the
handful of constants that may be used in the code itself, there is a new
The project parameter methods of the LlCore object have been marked as
"Obsolete" as well. Use the new ProjectParameters property of the ListLabel
The AutoDesignerFile property of the ListLabel object has been renamed to
AutoProjectFile. To ensure code compatibility the old property still exists,
however it has been marked as "Obsolete”.
The Fields property in the Dictionary object has been marked as "Obsolete”. Use
the Identifiers property instead.
The new default value of the property AutoDestination is now
LlPrintMode.Export (up to now: LlPrintMode.Preview). Thus all print targets are
available now as default.
The LlXSetParameter() method in the LlCore class has been marked as
"Obsolete". If you've implemented your own printing loop, you can ignore the this
warning. If you are using databinding you should use the 'ExportOptions'
property of the ListLabel class to set export options instead.
Some APIs that already had been marked as "Obsolete" in the previous version
are now private (e.g. LlDesignerProhibitAction()). Use the corresponding objects
(e.g. DesignerWorkspace.ProhibitedActions) instead.
The type of the sender argument passed to AutoDefineField and
AutoDefineVariable is ListLabel consistently.
11.2.3. Updating Projects Using the OCX (e.g. Visual Basic)
Load the Visual-Basic project (*.vbp resp. *.mak) in a text editor. Replace the line