...
Specify the parameter in the entry field — the field is visible only with the object field.! For processing many objects the entry field in the order edit form is used. For example, when processing a menu item, the quantity is expected to be specified into in the entry field. ! If this property is ticked, then the parameter, received at the time of processing the MCR algorithms, will be processed as if this information has been entered into the entry field. For example, 1234 is written on a magnetic strip; there is a MCR algorithm in the form of a prefix with the 123 prefix, with a Menu Item area, and a ticked Fill In Field by Entering Parameter tickbox Parameter in the Field box. When swiping the card the parameter will be designated as 4 (as a result of casting cutting off the 123 prefix). As a result, four portions of the dish will be added.
Application Area
Area – The area is a method for further processing the MCR algorithm or object type. Processing methods used without an object – employee, access card, menu item barcode, and menu item codespecified are Employee, Access Card, Menu Item Barcode, and Menu Item Code. In other cases, the object is set specified directly in the MCR algorithm.
Employee – means registering an employee in the system (including for confirming an operation). The parameter received after processing the MCR algorithm is compared to the Card Code employee attribute property (see the Account attribute property) and the matching employee is found.
Access Card – means processing the card at the time of accessentry.
Menu Item Barcode – searches means searching for a dish using the barcode and adds adding it to the order. The parameter received after processing the MCR algorithm is compared to the Barcodes menu item attributes and a match is found. The barcode can also include the information about the weight which should also be added to the parameter divided by a semicolon. An example of the MCR algorithm for processing dishes sold by weight in a standard delivery.
Menu Item Code – searching for the dish using the code and adding it to the order. The parameter received after processing the MCR algorithm is compared to the Code menu item attribute and a match is found.
...
The following is the function's prototype:
function ( Device: byte; // Device Type DeviceID: word; // Device ID const Src: pChar; // Input Data Indicator (received line) ResBuffer: pchar // An indicator of the buffer for placing the processed parameter line ): integer; stdcall; |
Returned value:
If the input data is of the right kind the function will return a number between 0 and 255. In this case this number is the length of the ResBuffer result. Numbers outside the 0...255 range indicate that the data does not fit into the algorithm.
...
Each script has a heading of the following type:
function ( DeviceSignal: Integer; // Device Signal sgXXXX DeviceIdent: Integer; // Device Identifier, see Device identifier var Parameter: String // At input– all information, at output – parameter ): Boolean; |
Returned value:
If TRUE then the script is considered to have worked correctly, and the parameter is taken from the Parameter variable.
The list of supported functions is given in the RK7Scripts.doc file.
Functions can also be requested from DLL. To do so it is necessary to create a MCR algorithm of the Script ver.7.0 type and a Script Header area. Such algorithms are not recognition algorithms and are used to set headers for other algorithms. In this case the Device Type property indicates that this header will be added only to the script of the algorithms supporting at least one device type from the list supported by the algorithm with the Script Header area. You need to announce the external function in the following way in the script field of such an algorithm:
function MessageBox(hWnd: Longint; lpText, lpCaption: PChar; uType: Longint): Longint; external 'MessageBoxA@user32.dll stdcall'; |
In this example:
MessageBox is the Function Name for calling from the
external script. It indicates that the function is external
MessageBoxA is the Function Name in DLL
user32.dll is the DLL Name
Stdcall points to the call's specification.
You can now call the function from the algorithm script:
MessageBox(0, ‘Some Text’, ‘Some Caption’, 0); |