The program description deals with the following:
The program is called up from window System -> User Interface -> Touch layout -> Touch page. The default values of the page layout are defined in Touch Layout and touch pages are linked to this layout via touchscreen. This program can also be used to customize individual function keys, i.e. keys can be blocked, the key events can be defined and the layout and key descriptors drawn up.
This program has a graphic user interface to allow the user to follow the changes made to the touch layout on the screen. A general description of this program can be found in the documentation "Layout program" and Touch layout.
Note:
The following details all options available for update of the basic data.
The following applies to this program:
Entry range permitted: alphanumeric max. 32 pos.
The entry in this field is dependent on the type of touch layout in use.
Text/Bit
If a screen layout of type "Non POS 30" is required the key
descriptors or the name of the graphic is entered here. With texts of several
lines the spacing is done with \n .
If for example the text Red wine is entered for a key and this is to be in two lines the entry would be "Red-\wine" .
The option "Pixmaps" must be set for bitmaps.
Backgr.Bitmap
If a layout type "POS 30", "POS 30 large, POS40 and POS 30
Pocket" are kept the name of the background graphic (e.g. the graphic for
a key) is entered here.
NOTE!
The background bitmap must exist as printed (.._dn.bmp) and normal (.._up.bmp).
Only the name of the bitmap without the ending ".._up.bmp" is
entered. Select one of the two types or enter the base name. The background
bitmap must exist in the directory of POS colour. "blue" in
"bmp\blue" directory, 1024 resolution in "bmp\blue\w1024" directory
and 1152 in "bmp\blue\w1152".
For layout types "POS 30", "POS 30 large" programming is always done with colour "blue". If another colour is required the bitmaps should also exist in the selected colour in the appropriate directory.
For layout type "POS 40" the colour is defined by the colour stated in the layout.
The key descriptor or the name of the graphic which is to appear on the key is entered in field "Foreg. Bit/Text".
Entry range permitted: alphanumeric max. 32 pos.
The entry in this field is dependent on the type of touch layout used.
· If a touch layout type "Non POS 30" is updated, no text is entered in this field. The key descriptor and/or the name of the graphic for a key, for a touch layout of this type is entered in field "Descriptor 1".
· If a touch layout type "POS 30", "POS 30" big" and POS 30 Pocket" is updated, the key descriptor and/or the name of the graphic which is to be under this key is entered.
Enter the description to be displayed on the key. Please note that the number of characters depends on the font and the font size used.
Line spacing is generated by \n. If, for example, the text Red wine is to be divided up into two lines, the entry should be Red \nwine
Entry range permitted: numeric 1 - 9999
This parameter defines the colour of the foreground, i.e. the lettering colour. The MICROS Retail OSCAR POS application standard provides a range of colours. Other colours can, however, be selected for the foreground and background.
The linkage of the colour to a colour ID and name can be found in the Color table.
The window for updating Colors appears after activation of the right-hand button. Colours can be mixed using entries for the various colour parts (red, green, blue).
The default colour is the one defined in the Touch Layout. If a different entry is required, the default value will be overwritten.
Entry range permitted: numeric 1 - 9999
The background colour of the key (= key face) is defined here. The MICROS Retail OSCAR POS application standard provides a range of colours. Other colours can, however, be selected for the foreground and background.
The linkage of the colour to a colour ID and name can be found in the Color table.
The window for updating Colors appears after activation of the right-hand button. Colours can be mixed using entries for the various colour parts (red, green, blue).
The default colour is the one defined in the Touch Layout. If a different entry is required, the default value will be overwritten.
Entry range permitted: numeric 1 - 999
Fonts programmed with Fonts are linked here. The number of the font required is entered here. The fonts can be updated after changing to the appropriate program with the right-hand button.
The default font is the one defined in Touch layout. If a different entry is required in this field, the default value should be overwritten.
Note:
Entry range permitted: numeric 1 - 999
Enter a value for the font size for the characters in the key descriptors.
Button active: Key with
graphic.
Button deactivated: Key without graphic.
If a graphic is shown on the key, the button should be activated and the name of the graphic should be entered in field "Descriptor 2".
Please note that the data format for graphics is dependent on the operating system. For example, UNIX supports the XPM format, WINDOWS NT supports the BMP format.
Button active: The key is
faded out.
Button deactivated: The key is visible.
Normally, the copy of a standard keyboard layout is updated with the highest possible number of keys.
This means that all keys should be on all pages. Keys which are not required should be deactivated by activating the button. Deactivated keys are marked in red in the lower left-hand corner. They are not shown on the page concerned.
Note:
New touch pages are added to an existing touch layout with button "Init.page." in program Touch
pages. A new touch page is created after activating this button. The new
touch page matches the layout type defined in program Touch layout.
Button activated:. When this
key event is called up the ASCII keyboard will be automatically displayed.
Button deactivated: When this key event is called up the ASCII keyboard
will not appear.
Note:
Key events which require additional entries of alphanumeric characters can be
set up in the program in such a way that the ASCII keyboard is shown
automatically after selection of the key event. Please note that this function
is normally disabled in program System -> User interface -> Touch layout
-> Add.data with parameter "Autom.Asc-Keyb.change".
Button activated:. The
general settings for the key layout do not apply .
Button deactivated: The globa settings for key layout apply.
If a touch layout type POS40 (Layout_40_1024 and Layout_40_1152 is in use the general settings for font and font size as defined in program System -> User interface -> Touch layout apply to various key groups (e.g. a predefined font size for normal item preset keys).
These defined values can be changed in this program if the option "Overwrite" (=overwrite touch layout setting) is activated.
Note:
The size of the keys and their positioning on the key field can be changed for
the touch layouts "Standard Layout (1)", "FastFood Layout
(2)", "Big Layout (3)", "PocketPC Layout (4)" und
"PocketPC Layout_H (5)" The options in groups Dimension, Screen
and Mode only apply to the stated touch
layouts.
The keys are shown on a maximum of 2 levels. Active and inactive keys are linked to their own level and they can be shown individually via the options in the group Screen.
The following options can be activated in group Screen:
Note:
The size of the keys and their positioning on the key field can be changed for
the touch layouts "Standard Layout (1)", "FastFood Layout
(2)", "Big Layout (3)", "PocketPC Layout (4)" und
"PocketPC Layout_H (5)" The options in groups Dimension, Screen
and Mode only apply to the stated touch
layouts.
The following options can be activated in group Mode:
Note:
The size of the keys and their positioning on the key field can be changed for
the touch layouts "Standard Layout (1)", "FastFood Layout
(2)", "Big Layout (3)", "PocketPC Layout (4)" und
"PocketPC Layout_H (5)" The options in groups Dimension, Screen
and Mode only apply to the stated touch
layouts.
The following options can be activated in group Dimension:
If the preset size of 54x54 Pixel for a key is to be changed please ensure that the key under it must be deactivated with option "Off" as otherwise the extended key will cover the it.
In addition to the selectable key dimensions the size of a key can be changed to an exact pixel value with option "Zoom" in group Mode and a change in the size.
Entry range permitted: numeric 0 - 9999
The horizontal position of the upper left pixels of a key is defined here. Counting begins in the upper left-hand corner of the right-hand sales touch page.
Entry range permitted: numeric 0 - 9999
The vertical position of the upper left pixels of a key is defined here. Counting begins in the upper left-hand corner of the right-hand sales touch page.
Entry range permitted: numeric 0 - 9999
The key width is stated in Pixel. The standard width is 54
Pixel. The value can be changed.
The default is the key width defined in the Touch
layout. If another entry is required in this field the default value will
be overwritten.
If a touch layout of type "POS 30", "POS 30" big" and "POS 30 Pocket" is updated, the width and height of the key are defined by the size of the background graphic.
If larger key pictures are required for touch layout of type "Non POS 30" the following should be noted:
Entry range permitted: numeric 0 - 9999
The height of the key is stated in Pixel. The details stated under Width also apply here.
Entry range permitted: alphanumeric max. 20 pos.
The name of the "Key event" released by a key depression is entered here. If an existing touch layout is to be processed, this field shows the event name currently programmed under this key. This event name can be changed by selecting the FSM group in field Group and by defining the appropriate keyboard event for this key in field Event.
Example:
To be able to record a department, DEPT should be entered. Call
up of the next touch page is possible, for example, with entry fTP.
A detailed description of all key events can be found in the documentation Key and booking functions.
Note:
This list of key events is drawn up by executing command "oscar
createEvents" in directory work. This is only possible for a new
installation or with a new release.
The FSMs FSM's (Finite State Machine) are searched for keyboard events and these are stored in a separate file in directory Verzeichnis"..\fsm\". During the validity period of the layout the operator can select the key event required via the fields Group and Event to link this function to a key.
Button activated: When the
FMS event of a FMS group is selected only the preset events are displayed, e.g.
fPM, fDICS etc.
Button deactivated: When the FMS event of a FMS group is selected all
events are shown.
Button activated: When the
FMS event of a FMS group is selected no preset events will be
shown, e.g. fPM, fDICS etc.
Button deactivated: When the FMS event of a FMS group is selected all
events are shown.
Select the FSM Group in this field as the selection for the linked key events in field FSM Event.
The key events which are offered for selection in fields Group and Event must have been created in advance:
· This list of keyboard events is drawn up with command "oscar createEvents" in directory work. This command only needs to be executed for a new installation or after a release change.
· The FSMs (Finite State Machines) are searched for keyboard events and are stored in a separate file in directory "..\fsm\". When the layout program is called up, the key events can be selected via fields Group and Event to allow the function to be linked to a key.
·
The groups match the existing Finite State
Machines in directory "..\fsm\"
Gc.fsm
Functions for GuestChecks
Payment.fsm
Functions for payment types
Position.fsm
Functions for receipt positions
Receipt.fsm
Functions for receipts
Register.fsm
Functions for terminals
Specfunc.fsm
Special functions
Select the FSM event which is to be linked to the key.
The key events which can be selected in field Group and Event from a list must have already been generated:
· This list of keyboard events is drawn up with command "oscar createEvents" in directory work. This command only needs to be executed for a new installation or after a release change.
· The FSMs (Finite State Machines) are searched for keyboard events and are stored in a separate file in directory "..\fsm\". When the layout program is called up, the key events can be selected via fields Group and Event to allow the function to be linked to a key.
·
The groups match the existing Finite State
Machines in directory "..\fsm\"
Gc.fsm
Functions for GuestChecks
Payment.fsm
Functions for payment types
Position.fsm
Functions for receipt positions
Receipt.fsm
Functions for receipts
Register.fsm
Functions for terminals
Specfunc.fsm
Special functions
Entry range permitted: alphanumeric max. 20 pos.
Enter the data which is to be transferred from depression of the key. For example, for an article preset key (entry under Event Name: FW) the article no. to be recorded would be entered, for call up of a touch page (via fTP) the appropriate page name. The name must be identical to the entry in field Descriptor in window Touch page.