|
Speed-Up and Enhancements:
-
The management of the standard frame grabber parameters was
improved in the following way:
-
The parameter settings are persistently stored in the DSC file
for each frame grabber separately.
-
There is now a button in the AVTViewFG support tool/dialog for
resetting the frame grabber parameters to sensible default
values.
As a result, frame grabber parameters in DSC files created using an
older ActivVisionTools version are not read correctly and must
be restored manually.
-
AVTView now has two properties AllowEditROIConfig/AllowEditROIAppl,
which determine if an ROI can be modified in
configuration/application mode. These are also accessible via the
support tool AVTViewConfigExec.
Functionality:
-
AVTViewDisplayModes now provides two additional color parameters,
which are used mark ROIs evaluated as 'not okay' and for
highlighting objects selected in ActivDataView or in the tree of
AVTDecision.
-
A busy cursor is displayed during grabbing.
-
AVTView provides the new property EnableWriteToDCSFile, which
enables or disables the writing to the description
file. Furthermore, the method WriteToDSC, which is called by the
AVTProjectManager whenever the project is saved, is now also
available via the programming interface.
-
It is now possible to enter the length of the line in
AVTViewCalibration while the application is running.
-
Pasting an ROI now causes an immediate calculation of results.
Changes in the Programming Interface:
-
The following properties and methods of AVTView have been renamed
or removed. The following list shows the new names or specifies the
new method which should be used by the user to accomplish the same
task:
- DrawMode -> DisplayMode
- AddViewData -> AddOverlay
- Reset(All)ViewData -> RemoveOverlays
- No longer required
- DisplayAllAction -> RefreshDisplay
- DisplayResultsROIAction -> RefreshDisplay
- AddROI -> CreateROI*
- RemoveROI -> DeleteROI, DeleteROIByName
- HROI* -> AVTROI*
- AVTROIClass.Init -> Use AVTView.CreateROI* to create
ROIs
- ExecuteAllToolsContinously ->
ExecuteAllToolsContinuously
-
The representation of a line ROI has changed, such that the
direction of the line is from the first point to the second point,
as intuitively expected. A side effect is that line ROIs of old
projects will have a reversed direction. The most simple way to fix
this is to modify the ROI in the GUI. If this is undesirable,
because the positional information is delicate, you can also modify
the entry in the DSC file, by exchanging the names of the
coordinate tags Row1,Col1 and Row2,Col2 for the line ROI, e.g.,
AVTView1 AVTMeasure1.ROI_0_ROIKind L 3
AVTView1 AVTMeasure1.ROI_0_ROIName S Line_1
AVTView1 AVTMeasure1.ROI_0_Row1 I 159
AVTView1 AVTMeasure1.ROI_0_Col1 I 451
AVTView1 AVTMeasure1.ROI_0_Row2 I 160
AVTView1 AVTMeasure1.ROI_0_Col2 I 136
becomes
AVTView1 AVTMeasure1.ROI_0_ROIKind L 3
AVTView1 AVTMeasure1.ROI_0_ROIName S Line_1
AVTView1 AVTMeasure1.ROI_0_Row2 I 159
AVTView1 AVTMeasure1.ROI_0_Col2 I 451
AVTView1 AVTMeasure1.ROI_0_Row1 I 160
AVTView1 AVTMeasure1.ROI_0_Col1 I 136
Bug Fixes:
-
It is no longer possible to paste an ROI if the active tool is
incompatible with this ROI's type.
-
If a grab failed, the AVTView property FGParallelGrabbing was set
to false and the grab was repeated. This is now only done if the
grab failed because parallel grabbing was not supported by the
frame grabber.
-
Tools are now correctly re-executed when a minimal ROI is
generated.
-
The zoom position in AVTView is now correctly made persistent.
Manual:
-
The User's Manual for ActivView is available in a new
edition. It has been updated and extended to reflect the changes in
ActivVisionTools 2.1.
-
The example Visual Basic projects have been adapted to version 2.1.
|