Specifications

Corrected and Known Anomalies
SpectroWATCH
Software Release Notes Page 128
SpectroWATCH
Corrected SpectroWATCH Anomalies in SPECTRUM 6.0
1 A segmentation violation no longer occurs when you attempt to Jump
to a model/watch of a model type when that model type’s folder is
collapsed.
2 When a watch is modified in a way that causes its status to change,
the status of that watch is now the same in the Watch Manager and
Watch Editor applications.
3 When the VNM is highlighted in the Watch Editor and you hold down
the control key to highlight more than one watch, a segmentation
violation no longer occurs.
4 On the Windows NT platform, the Watch Editor no longer shuts down
when attempting to reenter Alarm Descriptions after previously
deleting an Alarm Description.
5 In Watch Editor, the error dialog box no longer freezes after clicking
OK when trying to destroy watches which are referenced by other
watches.
6 In both Watch Manager and Watch Editor on the Windows NT
platform, the labels of some pull-down menus, buttons, tool tips,
lists, and names of watches are no longer prefixed by tagged strings
such as CsTS, CsTSpqui, etc.
Known SpectroWATCH Anomalies in
SPECTRUM 6.0
Problem 1: Watches which produce a result that is greater than a 32-bit
integer cause an error message to appear in the watch’s Status in Watch
Editor which reads:
Failed - Overflow in binaryoperator. ,
and the message,