1.1 Critical Items

1.2 Known Limitations

1.3 Enhancements

1.3.1 DataLogger – changes in display of measurement values

DataLogger display has been modified to show the type of a variable along with its measurement value. The type will be enclosed in parenthesis preceding the measurement value. (as shown in fig above).

• (NTYPE) – for boolean data
• (ITYPE) – for integer data
• (RTYPE) – for decimal data
• (TTYPE) – for text data
• (DTYPE) – for digital data
• (XTYPE) – for 85 subset’s connection data
• (X89TP) – for 89 subset’s connection data

Similar output in an old style DataLogger shown below.

1.3.2 IRS232Resource modified

There are 6 new properties added to the IRS232Resource.

      [propput, id(17), helpstring("property RTSLine")]

HRESULT RTSLine([in] VARIANT_BOOL newVal);

      [propput, id(18), helpstring("property DTRLine")]

HRESULT DTRLine([in] VARIANT_BOOL newVal);

      [propget, id(19), helpstring("property CTSLine")]

HRESULT CTSLine([out, retval] VARIANT_BOOL *pVal);

      [propget, id(20), helpstring("property DSRLine")]

HRESULT DSRLine([out, retval] VARIANT_BOOL *pVal);

      [propget, id(21), helpstring("property RINGLine")]

HRESULT RINGLine([out, retval] VARIANT_BOOL *pVal);

      [propget, id(22), helpstring("property RLSDLine")]

 HRESULT RLSDLine([out, retval] VARIANT_BOOL *pVal);

The first two properties allow the user to set the state of the "RTSLine" and the "DTRLine" to high or low. VARIANT_TRUE indicating "high" and VARIANT_FALSE indicating "low".

The four other properties retrieve the status of the "CTSLine", "DSRLine", "RINGLine" and the "RLSDLine". VARIANT_TRUE indicating "high" and VARIANT_FALSE indicating "low".

1.3.3 Opening a Resource modifications

This release of the WRTS has an implementation related behavioral change managed behind the scenes. This change will not modify any current functionality of the WRTS.

ATLAS "ENABLE" for a resource translates to opening the resource (in case of a file). However, in some conditions an ATLAS program could call "ENABLE" for the same resource a second time without "DISABLE" disabling it. [This is allowed by ATLAS without flagging errors, user(s) may neglect calling "DISABLE" on a prior "ENABLE" resource]. In such situations when an "ENABLE" was called again for an already opened resource, the WRTS used to close the resource, before opening it again. This was a generic behavior followed by the WRTS for all resources.

This behavior of the WRTS was found to be limiting. The current release of the WRTS delegates the handling of additional "ENABLE"(s) to the concerned resource. Various resources have been updated to handle such a situation on a per resource basis.

Example: The file resource continues to follow the old behavior. If an "ENABLE" for a file resource is called twice for the same file, the second "ENABLE" will close and reopen the file.

Example: The socket resource has a modified behavior. If an an "ENABLE" for a socket resource is called twice, the second "ENABLE" is disregarded, thus saving time on closing and opening of a socket again.

1.3.4 New Interface IOLESpecifyPropertyPages defined in ComUtil.dll

[

            object,

            uuid(3F6B2601-F0DA-11D2-BBB0-00C0268914D3),

            oleautomation,

            helpstring("IOLESpecifyPropertyPages Interface"),

            pointer_default(unique)

      ]

      interface IOLESpecifyPropertyPages : IUnknown

      {

            [helpstring("method GetPages")]

HRESULT GetPages([out,retval] VARIANT* pPages);

      };