...
By including only the attribute, so without file name, parameter name or value, the current value of this parameter will be used as the QBinaryID search key.
Please note that in the event of a VALUE parameter the formatted value of the parameter will be used as search key. Thus, a value of 2 will be provided as 2.00 if a Fixed Format with 2 decimals () is used. Note that a QBinaryID string of 2 will not fulfil this argument value. The used value will be the parameter value of the current solution/dataset/object/case. Parameters not having the single attribute will not be linked to images in this fashion.
...
The first limitation implies that if you want to present the same image for multiple values you need to introduce multiple instances of an image in , one of each value that may occur. In order to get around this limitation, it is possible to provide a Boolean expression for QBinaryID instead of a single value. The expression need to be preceded by @. Examples are:
In fig.1 the constraint is connected to Figure 6.gif. For any value >3 and <9, the image Figure 6.gif will be shown. In the constraint all intrinsic Quaestor functions intrinsic Quaestor functions can be used including brackets. However, functions using objects are not evaluated.
...
The second limitation of Method 5 is related to generic parameters. Generic parameters have object dependent references, each containing e.g. sets of option lists that of that are solely related to particular objects. This implies that one wishes to relate images not only to parameter values but also to the object in which the value exists, i.e. it may become necessary to relate ImageAto relate to value X of Par_i in object Obj_j and !ImageB to value X of Par_i in object Obj_kof in object and ! to value of in object .The way to do this is to use the lists in the in the object-related references as in the following example from a parameter Switch.
...
will be available. In this object, for a Switch value a value of -1 the Dataset.QBinaries.qBinary with the with QBinaryID value of 12 will be shown in the Illustration form. For a Switch value of 1 theDataset.QBinaries.QBinary with the with QBinaryID value of 13 will be shown. The attribute @PICTURE is attribute is included in order to tell Quaestor that tell Quaestor that it should search for an image/object inDataset.Binariesin.
In any instance of the object Diesel.HTCooler this will be picture 14 and 15 respectively. This example shows how to relate different images to the same parameter value in different object instances.
...