Creating buttons

helps select table of contents previous Oben next german version

Demo_336_UsrManagement as an exampleSetting up a user managementPagesChanging a passwordCreating buttons

 

New password:

Password verify:

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:

BtnLbl_Cancel

Cancel

Cancel

etc.

Serves the creation of titles in various languages.

Lbl_PwVerify

Password verify:

Password verify:

etc.

 

 

Button:

Application:

Function:

Btn_Cancel

Exit user management without saving changes.

Selecting a screen page [OperationMenu]

Btn_PwChange

Concludes password change dialogue by accepting the changed password and calls up start page.

Change password

 

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 then moves into the foreground, with the text list positioned behind.

 

 

 

See also:

 

Kapitelseite Creating touch fields or buttons

 

 

<< return