Images
All image files that appear in the mask field
attributes or as constant text in the commands ON … MACRO, MESSAGEBOX, LOAD_PICTURE, MOVE_PICTURE, GET_IMAGE_HEIGHT, GET_IMAGE_WIDTH, SET_SPLIT_WINDOW_HEADER or
that were specified by #ADD_IMAGE are included in the
program-jar-file, which is created in the Generator .
Images that are called by a variable cannot be included since the content of
the variable is unknown at the time when the program is generated.
Examples:
ON F2 MACRO SEARCH.CUSTOMER,"@search.png,Search"
H% = LOAD_PICTURE(3,5,0,0,0,1,"Test.gif")
The images search.png and Test.gif are included
in the program-jar-file.
H$ = "@search2.png,Search"
ON F2 MACRO SEARCH.CUSTOMER,H$
IMAGE$ = "Test.gif"
H% = LOAD_PICTURE(3,5,0,0,0,1,IMAGE$)
The images search2.png and Test.gif cannot be
included in the program-jar-file since the content of H$ and IMAGE$ is unknown
at the time of generation.
The Ebus program always tries to first load the
images from the program-jar-file. If the image cannot be found there, the
program will try to load it from the hard disk.
With 2T programs images are included in the
Client-jar-file as well as in the Server-jar-file. The advantage is that images
shown by the Server can be loaded directly from the Client-jar-file and do not
have to be transferred from Server to Client first. Images that are loaded in
the Server program (e.g. LPRINT_PICTURE), can be read from the
Server-jar-file.