Datasheet

EA uniTFT Vorläufig
deleted in a targeted manner, and others can remain in place.
Below is an example, to make it clear how handling objects works.
Once the display has been started, a main menu is opened, with a background (ID=100), Logo(ID=101) and two
touch buttons(ID= 1,2) for selecting the sub-menu. A button style(number=1) is, furthermore, defined for the
touch control buttons.
The background, logo and button style should also be present in the sub-menus. In order not to overwrite these
objects, using the object IDs should be discontinued. A heading with a corresponding style, as well as a line, are
supposed to be generated in Menu 1. All objects still existing that are no longer required are to be deleted in
advance.In this case that is Objects 1 to 99. The deletion is performed by entering the delete command for
objects(→ #ODI 1-99). he result can be seen in the figure below.
Naturally, the objects in Menu 1 and Menu 2 can be used in the same way.
COMMAND SYNTAX
A command always begins with '#'. Subsequently there is a 3-digit sequence of digits - the command code.
Depending upon the command code, further parameters are required. In order to separate the parameters, one
of the following characters needs to be used:
l Space
l Comma( , )
l Full stop( . )
l A semicolon ( ; ) (only and mandatorily at the end of a string)
l Specified range of multiple object IDs: '-' sign: e.g. 1-5, instead of 1,2,3,4,5.
The command always needs to be concluded by an LF (line feed) Should the line feed not exist, the command is
not executed.
Example::
Technische Änderung vorbehalten.
Wir übernehmen keine Haftung für Druckfehler und Applikationsbeispiele..
Seite 7