Page History

...

 Add the relation above to the class geometry. The parameters are automatically created when entering a relation. Frame should be listed as a user defined (VR) parameter and Rel_B should be System defined (SYS). Don’t forget the dimensions (Rel_B and Frame are dimensionless), and a proper reference for the parameters.

...

The syntax defines a Function that creates an object Waterline including Rel_B and Frame the moment it is initiated (when you do a calculation). The first parameter, @Rel_B, makes sure Rel_B is the top goal (calculated value). The second parameter, @Frame, makes sureFrame is the input for the function, the expression following @Frame: STR$(StartFrame) + "(" + STR$(FrameStep) + ")" + STR$(EndFrame) defines what should be asked as input to create the range input within the Waterline object. 

...

The solution is the object Waterline, which is filled with values for Rel_B  for every case of Frame. Please note that the parameters are requested in alphabetical order. By using the @ORDER attribute in the data slot of the parameters you can manipulate this order (provide @ORDER:1 to StartFrame, @ORDER:2 to FrameStep and @ORDER:3 to EndFrame). Furthermore, please note that you cannot select Waterline as top goal when you are into the Waterline object in one of the solutions. The reason is that Quaestor assumes you want to add a parameter to this level and does not allow you to do so.

...

The TeLiTab format used to describe the contents of the object is clearly visible. There is 1 list item, named "Waterline". This is a telitab (2nd level), containing 0 list items and a table with 2 parameters, Frame and Rel_B. The case numbers are shown between double quotes ("").

...