Page 1 of 18. Showing 173 results (0.011 seconds)
QBinaries object
The QBinaries object is a reserved object to store binary data. Please note that it can be used for any data (pictures, MSWord files, CAD files, etc.). Below a description is given how to create this object with content. Basically there are three steps: Creating the reserved parameters; Adding them to the datasetUsing objects
and Access Next to the direct use of Quaestor objects as functions, it is possible to refer and use value from these objects in expressions … Using Quaestor objects Quaestor employs a powerful ‘parameter’ concept, i.e. a parameter can be a numerical attribute like length, mass and cost, but also@OBJECT
The relation attribute @OBJECT is used to define the location of the data stored in the data slot of the specified name, useful if multiple relations are using the same static set of data. Syntax Place @OBJECT:ParameterName in the data slot of the relation Arguments ParameterName is the internal nameAn object in Quaestor
In computer science an object is a language mechanism for binding data with methods that operate on that data. In information processing an information source for an information processor. In Quaestor a parameter can be an object (or an object is defined by a parameter) which binds data with methods operatingTutorial 2: Objects and TeLiTabs
that Rel_B and Frame are to be calculated in the object. See also QuaestorSyntax. Note that just after you have created the expression, Waterline appears as a new … Tutorial 2 Objects and TeLiTabs Learning goals Learn about the TeLiTab data format Using an object as a function Creating a multiple case solutionADDGOALS
http://mods.marin.nl/display/QUAESTOR/TeLiTab or Object, in combination with the forced goals (SubGoal http://mods.marin.nl/display/QUAESTOR/SubGoal), the value, expression, TeLiTab … Method 1 GoalValExp http://mods.marin.nl/display/QUAESTOR/GoalValExp (a ValExp) is the parameter or expression that should be the result of the function; SubGoalMirceaKE.xml
EXPRESSION, OW, AND, PHYSICAL, CLASS 0, EPS 0, TR, INI 1, COL 9, FF 2, NN, USR, VALUE, OUT, NO</DefaultFrameAttributes> </General> <DefaultPaths> <KBs>C … </ProposedRelations> <RequestedOrDetermined>true</RequestedOrDetermined> <UsedInExpressions>true</UsedInExpressions> <Expression>true</ExpressionDefault user.xml
> <AutomaticUpdates>false</AutomaticUpdates> <PingCheck>false</PingCheck> <DefaultFrameAttributes>HARD EXPRESSION, OW, AND, PHYSICAL, CLASS 0, EPS 0, TR, INI 1 … > <RequestedOrDetermined>true</RequestedOrDetermined> <UsedInExpressions>false</UsedInExpressions> <Expression>true</Expression> <RelationsDataSlotWINWORD$
of values and use additional attributes in the data slot of the expression. For example, within a "Calculation" object you have done calculations on one or more Rigs … ... Target$ is a string expression containing the name of the document to be created (use for instance the TIME() and ORCA() functions for the generation of this name@OBJECTTITLE
The parameter or relation attribute @OBJECTTITLE is used to define that the parameter or expression is evaluated and shown as object title in the Workbase … or an expression Remarks This attribute is used in objects and makes it possible to show the object by means of a dynamic name. E.g., QEntity has