Creating buttons

helps select table of contents previous Oben next german version

Demo_336_UsrManagement as an exampleSetting up a user managementPagesUser loginCreating buttons

 

User name:

Password:

Creating buttons:

 

 

One button is needed for the user login. This is realised in the form of a touch field with graphics list and 2 image objects (button normal, button pressed). The following functions were allocated to the touch field: "Login" for carrying out the login, and "Selecting a screen page" which calls up the "OperationMenu" page.

 

To avoid having to create 2 individual image objects for each language, the text on the button was created via a text list. On this list, the titles of the available languages are defined.

 

Button:

Title:

Application:

Lbl_LoginBtn

Login

Login

etc.

Serves the creation of titles in various languages.

 

Button:

Application:

Function

Btn_Login2

Registers the user classified by user name and password with the user management.

Selecting a screen page [OperationMenu]

 

Button normal

Button pressed

Btn_Object_r

Btn_Object_p

Btn_Object_r.gif

Btn_Object_p.gif

 

The button's graphics were dimensioned such that they fit exactly into the gap in the input screen, and were integrated into the graphics list of the touch fields.

 

Although the text lists of the inscriptions can be positioned onto the button, they will disappear as soon as the button comes into focus by being clicked on. The reason for this is that the image object moves to the foreground, thus positioning the text list behind it.

 

 

 

See also:

 

Kapitelseite Creating touch fields for buttons

 

 

<< return