Page History
...
In the My Knowledge\Kbs\_KnowledebaseName\Html\images directory one can store a collection of images related to this knowledge base which can be referred to by including in the parameters' data slot or (object related) reference an attribute:
@PICTURE:FigureX.gif
FigureX.gif needs to be present in the above mentioned directory. If not, the standard background picture will be shown in the manner described above.
...
It is also possible to include an image (object) in a frame by the menu option Include Binary in Frame.
So if you include and include FigureX.gif and you write in the data slot: @PICTURE:FigureX.gif Quaestor will first save the binary and than show it as the picture.
...
If we use the QBinaries database, we ensure the availability of a collection of images independent from the name or location of a knowledge base. In this case we have several ways in which we can make an image appear. By introducing the attribute:
@PICTURE::5
in a frame, the image Figure 5.gif will be presented as soon you reach this frame in the knowledge browser (in the knowledge base presented in fig.1). Please note the double semicolon in which in@PICTURE::5 which is used to distinguish the value 5 from a file name. in this way, it is possible to show a single image on multiple locations without redundancy. Based on the value behind the double semicolon, the QBinary image value in the first record in with in Dataset.QBinaries with a QBinaryID value of 5 will be presented.
...
Instead of immediately referring to a file one can refer to another parameter:
@PICTURE:Lpp
If the parameter Lpp contains a picture reference like the methods described above, this reference is inherited by the frame containing the attributethe @PICTURE:Lpp attribute.
This method will work in combination with all methods 1-3.
...
Instead of a Knowledge Browser-centered approach to presenting images/objects, one can connect images to parameter values.
By including only the attributethe @PICTURE 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 (FF2) 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 single @PICTURE attribute will not be linked to images in this fashion.
...
if you want to present the same image for multiple values, you need to introduce multiple instances of an image in Dataset.QBinaries;
- Generic parameters can have object dependent references, each containing sets of option lists 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.
...
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
Dataset.QBinaries, 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:
@ParX=1 OR ParX=2 OR ParX2=6
@ParX=>1 AND ParX<6
In fig.1 the constraint is constraint @a>3 AND a<9 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 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 that of option lists 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 to value X of in object and to value of in object relate ImageA to value X of Par_i in object Obj_j and !ImageB to value X of Par_i in object Obj_k .The way to do this is to use the in the lists in the object-related references as in the following example from a parameter Switch.
...
will be available. In this object, for a value a Switch value of -1 the with the Dataset.QBinaries.qBinary with QBinaryID value of 12 will be shown in the Illustration form. For a Switch value of 1 the with theDataset.QBinaries.QBinary with QBinaryID value of 13 will be shown. The attribute is attribute @PICTURE is included in order to tell Quaestor that it should search for an image/object inDataset.Binaries .
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.
...
In the above picture, some parameters like and like ConfigType$ and some values of image of MainLTCoolerType$ image references are included.
For instance, the fifth case value of is in of ConfigType$ is separated:5 in which 5 is considered to be a reference a Dataset.QBinaries.QBinaryID reference to an image. In this example, the object the Dataset.Options object is data source to an script an |OPTIONS| script for parameter OPTIONS# , a TeLiTab set in which all elements of a case of will of Dataset.Options will be its value. The script The |OPTIONS| script is discussed in a separate article Data use and management in Quaestor.
The script The |OPTIONS| script results in invoking a list view including a browser component that will present the referred to image per parameter that is proposed in the list view. This allows a stepwise selection of a database record supported by images that are context sensitive, i.e. for each step in the selection process, it now possible to present relevant graphical images(, spreadsheet, pfd documents, etc).
...
Overview
Content Tools