Paper menus produce

First a paper menu must be produced, e.g., with Excel and be fastened on the Digitalisiertablett or – table.

The orders which lie behind the menu fields are deposited in a file by the type.men.

contains and in the next line him or the orders which should be explained if the user clicks on the field.

The field on the top left has the number 1, then is numbered serially from the left to the right and from above down. So that the processing of the orders cannot be interrupted by inputs of the menu line, an <ESC <sign should stand before every order<<.

Afterwards the situation of the paper menu and the place *.men – file must be informed of the programme. In addition there is the ordering MEN.

The menus are loaded with the order MEN and remain in the Workfile, until they are extinguished or are substituted with a new definition.

In the dialogue the user is asked for the number of the menu, afterwards he should digitize the corners of the menu and give last the file of the type.men in which the orders of the menu are deposited.

To reload a *.men file without digitizing the situation of the menu anew there is the parametre MEN/NOPOSITION.

Converting occurs in two steps. With the first step the biggest part of the way is bridged between both formats by Gradismenüs and Moskito's menus. Then there follows the control and fine adaptation.

In the list Tools\nt there is the programme convmenu.exe. With this programme the structure of a Gradismenüs can be moved in a Moskito's menu. With

if the menu gradis.men is converted into an equivalent menu moskito.men for Moskito.

Not all delicacies are considered by the converter. It has turned out necessary to check every menu field once for function. Besides, the following list has arisen with other adaptations:

GRADIS order	Explanation / conversion to Moskito / albatross orders
AOA	This order serves only to give a Flag to the identified object which registers that this object was changed. A change is necessary only if no other change in the object occurred, can be lost in most menu fields. => COMPULSORY HEALTH INSURANCE SCHEME IN 9600 DOK 9600
APT	Regulation of construction points => IEL APT
ATX LBL/QUE	=> ATX QUE
BTR	Store of plans with writing authorisation in the albatross => FORMAT / SYNC LOA
DECAGRAM	Selection of all objects with the object key an and extinguish of this key in all objects => This order / this menu field becomes mostly superfluous with Moskito!
DR1	Object extinguish => DOB
DRF	=> DRA
EQU x	This order is used to cover the same order sequences to another field of the tray menu. If for example, the order EQU 005 stands in the field 006, this means that above the field 006 the same functionalities can be clicked like in the field 005. There originates de facto a bigger counter field on the paper menu. => (orders to be used see field x)
ETR	=> SAVE
IGT	IGT ordinarily generates a graphic carrier object, i.e. an object with the "temporary" object key in 9500 which is not implemented in the data model. => Object in 9500 If the order IS1 with the parametre Key/xxx appears by the order IGT within a menu field, is valid the following conversion regulation: IGT = >Object xxx IS1 key/xxx = >ISAgen
Name / value INI	=> INI name worth
IS1	IS1 generates the primary key (ISA) in a graphic carrier object. If instead of a graphic carrier object already an object with "right" object key exists, the order ISAgen can be put, instead. => ISAgen
JOB	Identify of an object. Perhaps available parametres must be just taken over. => IOB/REPEAT
LEN	Calculation of the length of an element => CAL
MES	=> Echo/NOW (text from message table)
MFL	Explain of a macro. The first order MFL appearing in a menu is substituted with the order MFL_1, second by the order MFL_2, etc. => MFL_1 or. MFL_2, etc.
PPT	=> OBJ KEY / IN 7999 INI ModeRPT 1 STREET DKY / 1 COL / 168,0,255 INI ModeRPT 0 s. GeneralParallels / BUFFER/ORTHO #CLS s. GeneralParallels / BUFFER/ORTHO #CLS OpenElement 1 dob j s. Echo/NOWINDOW OK VWS
RG1	List to one In / "FM object" accompanying FM-Tupels. => IOB/REPEAT RG1
RED NAM / 1	=> RED/HOR
RT1	Takeover of attributes and attribute values from an authoritative table in a GRADIS object. The parametres must be moved: TYPE RT1 / 1 = >s. GetAttributsFromDatabaseDialog VERSION / 1... etc.
SAT	This order serves putting in or queries of attribute values, as a rule this is a value of the attribute OGN. There are different types of the order: TYPE SAT / 1.1 LBL/OGN => Begin Declare sat Echo/NOW \n\nOGN give Value sat io_Text () %% input c_if "s_strlen (Value (sat))" INI OGN Value (sat) c_else Echo!! OGN not sedate c_endIf TYPE SAT / 1.2 => Begin Declare sat Declare sat2 Echo/NOW \n\nOGN give Value sat io_Text () %% input c_if "s_strlen (Value (sat))" INI OGN Value (sat) c_else Echo!! OGN not sedate c_endIf Echo/NOW \n\nZON give Value sat2 io_Text () %% input c_if "s_strlen (Value (sat2))" INI ZON Value (sat2) c_else Echo!! ZON not sedate c_endIf Here becomes one or two variables who are used in the following order are put: TYPE SAT / 2 = >s. AddAttribut OGN Value (OGN)
SEL SKY	=> SEL KEY
SSN	similarly to SSH => SSH
TEX/xxx	Texts from the text buffer take over => %% input db_GetTextbuffer (xxx)
TGI	Generate of an attribute text The sign key (DKY), the text height (TXI) and the text kind (TXM) as well as the attributes which should appear attribute text stand in the table TgTab.tab and must be read with the conversion from there for the in each case suitable object key. This order can have different stamping which is fixed by the parametre Type / a, b, c, d: a gives the text direction: If a=1 (text horizontally) => THO if a=2 (text positioned) => TPO if a=3 (text in parallel) => TPA b gives the version number, with it the number is meant in the second column of the table TgTAB.tab. She determines in addition to the object key in the first column which DKY, TXI, TXM and attributes must be used. c gives whether a text or several texts should be positioned. if c=1 => 1 text position => order only once move. if c=2 => several texts position => parametre / MULTINATIONAL place. d gives a fire-fighting option: 1 => old texts extinguish 2 => old texts do not extinguish (this option was ignored with the conversion)
TGM	TGM adapted by attribute changes also the texts (now are become superfluous, because with the conversion attribute texts are created). => remove.
UAT	To memories of attributes By the call of the function with TYPE / a=1 the attributes given in the menu are fetched at the object open at the moment. By all following calls with TYPE / a=2 these attributes in the object open then are stored. TYPE UAT / 1.1 LBL/RNK => INI UATLBL RNK INI UATWERT DBquery (RNK from open object/noq) TYPE UAT / 2 => Begin Declare certainly s. Echo/now \n\nSoll the following attribute are taken over? \n\n s_concat (Value (UATLBL)":" Value (UATWERT)) \n Value certainly io_Text () %% input c_if "m_eq (Value (certainly) j)" s. Exec s_concat ("AddAttribut" Value (UATLBL)"" Value (UATWERT)) c_else s. Echo/now attribute was not taken over! c_endIf
URN	Change of all values of an attribute whose value should be changed in every object of the selection amount. => QTX/SEL
UVA	Integrate of an object into a logical context. The information of the parametres changes accordingly. TYPE UVA / 1,1.1 => LinkObjects LG / 1 CP / 1/RTB TYPE UVA / 1.1 => LinkObjects LG / 1 CP / 1
KEY / IN 1910	=> OBJ KEY / IN 1910 Defense Intelligence Agency DKY/xxx SYM/xxx TXI / 150 TXH / 5 TYPES / 1 OpenElement 1 / text OpenPoint 1 RTX MEL

after changes the result ERS DRA can be cancelled almost always. She disturbs only the expiry.

With some old GRADIS functions the parametres were renamed and must be adapted accordingly.

With the order Info box a tip window in which the work routine of the order can be explained can be inserted. This is to be inserted if necessary by hand.

A help text can be assigned to every menu field. This appears if the cursor above the field stands. This text must be inserted by hand. The text appear in the status line of the input window or the plan window. In addition becomes in the menu definition of the field 17