Postprocessor parameters inquiry while the first using

Sometimes a dealer does not know some specific information about the user machine. It is possible to make the data inquiry. In this case the user will be asked about the NC-system information and inputted data will be saved in the postprocessor file.

An *.sppx file of a postprocessor it's a regular XML file. So you can edit it by a simple text editor (Windows' Notepad for example, or it is better Notepad++ to get syntax highlighting) to organize the data inquiry. There is a <CommonDefinitions> section (or node in XML terminology). It is shown below. It is a textual representation of an information you define in the Machine information window.

You can add a special MakeQuery="True" attribute to any of the nodes. Then the value for this exact parameter will be asked from the user just after opening the postprocessor file.

For example if the section has the text below:

Then the next dialog will appear just after opening the postprocessor file (including the case of starting G-code generation from the SprutCAM directly):

If click Save then the data will be saved in the postprocessor file and the dialog will not arrear in the next time. If click OK then the NC program will be generated with the inputted data and the dialog will appear in the next time again. If click Cancel then the postprocessor file will not be opened (G-code will not be generated).

Additional information input

Sometimes it is useful to have the system query for the list of additional parameters and user must provide the values for each of this parameter before working with the postprocessor. It is possible. The list will appear in the machine information dialog. If the postprocessor file contain the specially formed <InitialQuestions> node then the "Additional information" panel with drop-down lists or edit fields appears. After the user provide some values inside these fields then the global variable corresponds to each parameter is initialized by the user input.

The <InitialQuestions> section format is shown below:

Where:

• "User visible text for the question" – the message for the user next to the input field.

• "Name_of_variable" – the name of any global variable that is available in the postprocessor (including custom programmer's variables defined in Common handler).

• "Type_of_variable" – The type of the variable. It can be one of three values: vtString for the String type, vtReal for the Real and vtInteger for the Integer types.

• "Default value of the variable" – the start value that will be assigned to the variable.

• If the variable should have only restricted set of values (drop down list) then define a non empty "<EnumValues>" section.

• "User visible caption of first possible value" – the user friendly value description.

• "Variable first possible value" – any value that should have the same type like the global variable.

• The text between "<!--" and "-->" is just a comment in the form of correct XML syntax.

• The syntax construction that starts with "<!CDATA[" and ends with "]]>" is required to be possible to input any characters set without breaking the correctness of XML.

An example for the <InitialQuestions> section is shown below:

The start input dialog will be the next:

After the save button is pressed the section will be the next:

And at the runtime the variables will have the next values:

• Variable1 = "Default variable 1 value 2";

• Variable2 = 9.98;

• Variable3 = 12345;

See also:

The main window