We think this is interesting, because menus on computer systems originally took their names from menus in Chinese Restaurants where the Chefs did not understand English, and the customers did not understand Chinese, but everyone could look up "Number 27" and know what it was.

Using Menus in PocketPos allows for the First level of options on the Sell Menu to be equivalent to the Pages in a restaurant Menu, and then the next level to be the items appearing on that page of the menu. It is a simple, fast, elegant solution, and has one other benefit... When menu items change, they are automatically updated in PocketPos, and the Pocket PC does not need to be reconfigured.

This means that there is very little configuration that needs to be done on PocketPos, however, you can change the layout of the sale header at the top of the screen, as well as the columns showing items on a sale.

Back to top

The entries in this section are as follows:-

Type= Must always be set to "W".

Input= Always set to "0" (zero).

Output= Always set to "2".

HeaderFont= Font for text displayed in header with 6 parameters separated by commas, being:-

• Font Name
• Point Size
• Escapement/Orientation in tenths o0f a degree. (rotation angle)
• Boldness scale from 0 (very light) to 1000 (very heavy)
• Italics 0=off, 1=on
• Underline 0=off, 1=on

HeaderDataN= Information about the data to be displayed with parameters as follows:-

• Type where "O" means Output Field, "I" means Input Field or "T" means Text literal.
• FieldName where the type is "O"utput or "I"nput and the actual text to display if type is "T"ext. Fieldnames for Output and Input fields appear in the table below.
• "X" coordinate (across) of the location to start displaying the data. This is expressed as a percentage of the width of the Sale Header Window.
• "Y" coordinate (down) of the location of start displaying the data. This is expressed as a percentage of the height of the Sale Header Window.
• "X" coordinate (across) of the location of the end of the area to display the data. This is expressed as a percentage of the width of the Sale Header Window. This applies only to "O"utput Fields. The width of "T"ext fields depends on the length of the text.
• "Y" coordinate (down) of the location of end of the area to display the data. This is expressed as a percentage of the height of the Sale Header Window. This applies only to "O"utput Fields. The height of "T"ext fields depends on the height of the font.

Field Name	Description
INPUT	This is a special field that is normally required in PocketPos, and is used to temporarily store data. In SELLmatix POS, you could sell a PLU by entering the PLU Number, and then pressing the "PLU" button. In PocketPos, you would do the same thing by entering the PLU Number into the INPUT field, and then selecting the PLU Option in the Regkey Menu.
LOCATION	Location Number for the order. This is normally used in a Restaurant or Bar environment when running Accounts for the table or Bar Location for the customers.
COMMENT	The comment entered into the sale header.
COVERS	The number of guests at the table. This is often used in a restaurant environment, but rarely used elsewhere.
ORDER NO	The order number supplied by the customer, to be quoted on invoices/statements.
CLERK NAME	Name of the Clerk Processing the sale. Rarely useful.
CUST NO	Customer Account Number if this is a charge sale.
CUST NAME	Customer Name.
ADDRESS 1	First Line of Customer Address.
ADDRESS 2	Second Line of Customer Address.
ADDRESS 3	Third Line of Customer Address.
ADDRESS 4	Fourth Line of Customer Address.
DATE	Date of the Sale
TIME	Time the sale started.
TOTAL	Total value of the sale.
BALANCE	Balance remaining to be paid on the sale.

Back to top

The number of columns displayed is automatically calculated from the number of entries in the ColumnHeaders, ColumnWidths and ColumnAlign entries. If you wish to have 3 columns, for example, then you should have 3 fields in each of these entries, separated by commas.

The entries in this section are as follows:-

ColumnHeaders=contains the headings that appear at the top of the columns, with each column separated by a comma.

ColumnWidths=contains the number representing the width of each column, with each column separated by a comma. The units used are added to calculate the total number of units, and in the example the total number of units is 120. In this example the first column is 10/120 th of the total width available. Note that the total width of the column display is reduced by the width of a vertical Scroll Bar, however, the scroll bar only appears when necessary.

ColumnAlign=contains the alignment flags for each of the columns, with each column separated by a comma. Valid Values are "L"eft, "C"enter, and "R"ight.

Clear Receipt=must always be set to "C".

NewSale=must always be set to "C".

SaleHeader=must always be set to "H".

Sale PLU=
Sale Memo=
Adjustment=
Payment=
Payment Change=
entries should all contain the names of fields that are to be displayed in the columns of the display, separated by commas.

The first field must always be an "L".

If no data is to be displayed in a column, such as in the "Sale Memo=" entry in the example, then this should be indicated by leaving the field name blank and inserting a comma. In this example, the first and second column for a memo would contain nothing, and the Description would contain the %DESC% field.

The Field names that can be used are as follows. These fieldnames must have a leading and trailing "%" character.

The FieldNames which can be used is the columns are the same as the fieldnames in the Line Dataset Variables used in other POS output. For a list of Line Dataset Variables, Click Here

Back to top