2 Visual Components Manuals

Introduction to Visual Components 2.3
arrangement for particular picture elements may also be used.
Note:
Color values have not changed. These can be taken directly from the data structure in the global color setting.
4.14.1.2 Changing Pictures
Visual Components V2.1 can now manage up to 65,000 pictures in a project. In earlier projects, only 250
pictures were possible.
If picture numbers are used in the project for changing pictures or for evaluating the current picture number, the
application (source) is to be modified as follows:
• Variable data types for changing pictures, as well as for the current picture number, have been changed
from USINT (8−bit) to UINT (16−bit). Therefore, the picture number or picture change data point has to
be changed to a UINT data type.
• 255 is no longer written to the variable to confirm a picture change. Instead, the variable takes the value
65535. In the application source code, the query for a successful picture change must now correspond
to 65535 and not 255.
Picture change variables which are not of type INT or UINT produce a compiler error.
VISU:(0):Error Variable for picture change from PLC "picture_number" must have data type of INT or
UINT
4.14.1.3 API Functions from the VISAPI Library
The VISAPI library introduced in version 2.0 has been substantially expanded (see also VISAPI Documentation).
Because of the ability to manage several projects on the target system, it became necessary to introduce an
additional parameter. This additional parameter specifies the target project (handle).
Furthermore, a few term names have changed.
It is therefore necessary to revise and test all functions programmed with the VISAPI. Existing functions will not
be changed for future upgrades.
4.14.1.4 Keys and Key Matrix for Touch Systems
Keys
In version 2.0, touch−based panel support was only available using a fixed grid of touch keys. Touch keys were
also only available in a fixed size.
In the current version, buttons or HotSpots can be represented in any size, position, function, and color − with or
without bitmaps or text.
Existing keys on a touch system are automatically converted to HotSpots. For each touch key, a dashed
rectangles is drawn on the display screen for the new HotSpot. The HotSpot takes over the properties of the
key.
These HotSpots can then be later moved and resized.
In many cases, these HotSpots can be switched to buttons to meet the necessary appearance requirements of
the application. In this way, the project becomes clearer (buttons instead of dynamic bitmaps and overlapping
HotSpots) and performance is improved (see also Creating Keys on the Touch Screen).
Key Matrix
The key matrix for touch−operated devices was set to a fixed grid (40 pixels x 40 pixels). Variables for changing
the key matrix received the touch position in an array of 192 bytes directly converted using the touch position.
This computation was based on the fixed 40x40 pixel grid.
Buttons and HotSpots status are currently transferred in the key matrix.
It is recommended to use buttons and HotSpots instead of the touch matrix used in the project parameters.
For this transition, one of two possibilities can be used:
4.14.1.2 Changing Pictures 445