Page History

...

Example 1, Use of data in the dataset with an |OPTION| script:

Assume a hull form offset table your want to store in a parameter HullForm$ because it is needed as part of an input file for hypothetical software to calculate e.g. hydrostatic properties.

...

HULLDATA# is the selected input set for the calculation and is defined by an |OPTIONSOPTIONS| script represented as a Telitab set in its data slot of the parameter:

...

The first line you see is simply an explaination (and not required).

The script between |OPTIONSOPTIONS|….| describes how, what and where to get the Telitab set you will refer to as HULLDATA#.

...

The "CAPTION" part is the presentation of the questions, the "OPTION" part is the link to the data in the data set that is used.

...

For instance when the ship type is already defined earlier in the solution, or is available as starting data in the dataset, you can add the relation HULLDATA# = QUERY#(0, SHIPTYPE$) to make sure that OPTION1 already that OPTION1 already uses the value for SHIPTYPE$.

Example 2, Use data in the data slot of the parameter with |OPTIONSOPTIONS| script:

As alternative method to select data, in stead of making a reference to an object as done with "DATA#" "ParentShips", you can include the data in the |OPTIONSOPTIONS|….| script of the parameter. This is done in the following example

...

@SUMMARY and @PICTURE are attribute, they manipulate the behaviour of the knowledge based system comparable to all the Slots&Properties. Using the @SUMMARY attribute you tell the system to display an overview of total selection made based on the dialog through de included data. @PICTURE tells that pictures should be displayed of which the references are given in the included dataset.

Again "CAPTION" and "OPTION" are the presentation and reference to the data. "SUMMARY" defines how the summary should be presented after the selection is made. Please note that the result corresponding with the summary number will be placed behind the text. Moreover, the order as they are presented in the scripts is the order of de lines as they are presented in the summary

By including "OPTION" in the the table, the database selection returns only a single value, being the selected case value of "OPTION" instead of all values related to the selection.

As mentioned the @PICTURE attribute defines that relevant picture information can be presented throught a references to these images. For "OPTION4OPTION4" this has been defined. For example, table 1:twind1 refers to an image "twind1" in QBinaries object in the Dataset (QBinaries is a reserved Quaestor object that can be used to store all knowledge base fixed binary data, see Image Management in Quaestor>topics>Technical documentation>).

...

Example 3, Use of binary data in the dataset with an |OPTION| script:

In the following we will show how to manage and access a set of binary objects. In this example we will enable the selection of components in a Rhinoceros configurator, a typical CAD application that can be controlled by scripts that are generated by Quaestor. The problem is related to the selection of component models on the basis of some selection criteria.

...

Quaestor employs an internal database selection mechanism that can be defined through an |OPTION| script. In the following we will briefly explain its principles. In order to enable the selection of a hullform, the following |OPTION| script is included in the data slot of the parameter ComponentFile$:

...