The screen() command controls the display of screens. It allows you to open sub screens such
as menus and also to close screens. This command only controls the screens, the screens themselves
are typically created in either UI files, XML files or directly in code.
Commnd Overview
system(Sub-Command)
screen(NAME)
Create the screen name by locating the UI file called name within the current parameters. Generally this means the
file 241_main.ui file or the 241_name.ui where 241 is the instance number, or selected User Interface in use. This is the most common method used
to display new screens.
User defined screens must start with a leading letter and can only contain the characters A..Z and 0..9 Names starting with a number are reserved
to Fieldpine
screen(1delete)
Close the current screen and remove all trace from the users viewpoint. When this command is used as a sequence of commands, such as on a button,
this command should not be followed by additional commands - there is no guarantee that subsequent commands will be processed after the screen is deleted.
If the setting ScreenDeleteDelay is defined (to a value in milliseconds), a pause is inserted after this command executes. This is typically used on
touch systems to allow operators time to remove their fingers and avoid double touching.
screen(standard(NAME))
Display an internal standardised screen. These screens are often used to perform dedicated but
isolated tasks at different times. The NAME parameter is generally the screen number, but can also
be the internal name in some cases.
| Number | Internal Name | Description | Links |
| 1 | | Capture product variant information |
| 2 | | Flow point information |
| 3 | | Select a product when a barcode resolves to multiple products |
| 4 | svcsetup | Display a control screen that allows entry of new SVC (prepay/loyalty) cards into the system. |
| 5 | | Select a single product |
| 6 | | Edit a single product |
| 7 | | Edit a single customer |
| 8 | | |
| 9 | | |
| 10 | | Prompt for a single charge account |
| 11 | | |
| 12 | | |
| 13 | | |
| 14 | | |
| 15 | | Prompt to select a single SVC/Prepay/Loyalty account |
| 16 | | Capture Eftpos payment amounts such as Cash out |
| 17 | | Display the list of expected sales that have not yet arrived. |
| 18 | | Select a single customer |
| 19 | | |
| 20 | | Select a single department |
| 21 | | Select a writeoff reason code |
| 22 | | |
| 23 | | Select a single supplier |
| 24 | | |
| 25 | | |
| 26 | | |
| 27 | | |
| 28 | | Prompt for a delivery address | Screen Details |
| 29 | | Prompt for a single employee |
| 30 | | Control online sales processing at this lane |
screen(1takesale)
Instructs this screen to "take" the current top sale and remove it from the stack. This command is designed solely for use
on sale completion screens where the sale is complete and should be removed from normal processing, but needs to remain
alive in order to display change values and other symbols.
screen(2name)
Create and process the screen name, and suspend operation of the current command stream until this screen
has closed. This can be considered to function like a subroutine call, or modal screen display. Most user screens
are created using this form of the command as modal screens are the least confusing to end users.
screen(3name)
Toggle mode. If the screen name is already displayed, make that screen topmost, if it is not active, then
create a new screen.
screen(4name)
Create a series of screens that are runtime generated rather than being statically defined. The keyword control
is used to select the method by which the new screen is automatically generated.
screen(1direct)
Not documented for customer use.
Remarks
Examples
This example shows a very common usage of the screen command, in this case a button is usually placed on the main User Interface screen, to display
an additional menu of commands, called the more screen by common convention. When this command is executed the POS locates the more screen definition
and displays that screen to the user.
screen(more)