InTouch 8.0 SP2
Last revision: 09/19/03
This document contains important information about InTouchÔ 8.0 with SP2. Please review this document carefully for known issues in this version and changes to the InTouch documentation included on this CD. InTouch 8.0 with SP2 provides support for InTouch on Tablet PCs. For more information on Tablet PC support, see InTouch 8.0 with SP2 Enhancements.
Known
Restrictions for Limited Users of InTouch
Known
Issues – InTouch 8.0 with SP2
InTouch
8.0 with SP2 Enhancements
To run InTouch, we recommend as a minimum the following hardware and software configurations:
· Any IBM® compatible PC with a Pentium II processor or higher (minimum: 400MHz on a single node system, recommended: 1.2GHz or higher).
· At least 2GB of free hard disk space.
· At least 256MB of random-access memory (RAM), 512MB of RAM is recommended.
· We recommend 5MB of additional RAM per 5K tagnames. For example, 32MB of RAM for 32K tagname support and 128MB of RAM for 60K tagname support.
· SVGA display adapter (2MB RAM recommended).
· We recommend you view WindowMaker in 800x600 resolution or higher to ensure full visibility of all dialog boxes.
· Pointing device. For example, mouse, trackball, touch screen.
· The Microsoft® Windows® 2000 Professional operating system with Service Pack 3 or higher or the Microsoft® Windows® XP Professional operating system with Service Pack 1 or higher.
· For InTouch Terminal Services, the Microsoft® Windows® 2000 Server(s) operating system(s) with Service Pack 3 or higher and with Windows Terminal Services enabled only in the Application Server mode.
· Tablet PC users must have the Windows XP Tablet PC Edition Version 2002 Service Pack 1 operating system.
· Tablet PC users must install Microsoft .NET Framework 1.1 manually before installing InTouch 8.0 with SP2.
Microsoft Windows Server 2003 Support and Requirements:
·
InTouch 8.0 with SP2
is supported on Microsoft Windows Server 2003 Standard Edition.
·
InTouch
8.0 with SP2 Terminal Services Edition is supported on Microsoft Windows Server
2003 Standard Edition with Terminal Server enabled (the default setting for
enabling Terminal Server on Windows Server 2003 Standard Edition is the
Application Server mode).
·
Running
InTouch 8.0 with SP2 on Microsoft Windows Server 2003 Standard Edition requires
the following system requirements as a minimum: 550MHz CPU speed on a single
node system (recommended: 1.2GHz or higher), 256MB RAM memory with at least
2.5GB free hard disk space.
·
Windows
Server 2003 Standard Edition Terminal Server client User Name(s) must be a
member of Windows “Remote Desktop Users” and “Power Users” groups in order to
connect to the server and to run any applications on the server.
·
Remote
Desktop Connection (RDC) – Connecting Windows based clients to Windows Server
2003 Terminal Server:
As an option, you can install Windows Remote Desktop Connection (RDC) to connect a Windows client to the Windows Server 2003 Terminal Server. This feature exists in Windows XP Professional but it has been enhanced for Windows Server 2003. The existing Terminal Services Client (Win32) software that was used to connect Windows clients to Windows 2000 Terminal Server can still be used to connect Windows clients to Windows Server 2003. Please refer to the following Microsoft Windows Server 2003 website for an overview of Terminal Services features and instructions on how to install “Remote Desktop Connection:”
http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx
· TSAC (Terminal Services Advanced Client) – Running InTouch in an Internet Explorer window on Windows Server 2003 Standard Edition Terminal Server:
To run InTouch 8.0 with SP2 in TSAC environment, “IIS” (Internet Information Services) must be installed on the server. This service is called “Application Server” in Windows Server 2003 and can be installed from Windows “Control Panel à Add/Remove Programs à Add/Remove Windows Components.” By default, this service is not installed as part of Windows Server 2003 installation.
To run InTouch 8.0 with SP2 in TSAC environment, “Remote Desktop Web Connection” must be installed on the server.
Please refer to the following Microsoft Windows Server 2003 website for an overview of Terminal Services features and instructions on how to install “Remote Desktop Web Connection”:
http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx
Note: Windows Server 2003 Terminal Server does not allow two clients login with the same user IDs. Each Terminal Services session has to have a unique user ID to connect to the Windows Server 2003 Terminal Server.
Citrix MetaFrame Support:
· To run InTouch 8.0 with SP2 Terminal Services ICA Thin client(s) on Windows Server 2003 Standard Edition, you'll need Citrix MetaFrame XP, Feature Release 3. Citrix MetaFrame 1.8 Feature Release 1 is not supported on Windows Server 2003.
InTouch Version 8.0 (or later) does not support the Microsoft Windows 3.x, the Microsoft Windows for Workgroups, the Microsoft Windows 9x or the Microsoft Windows NT operating systems.
NetDDE is not supported with InTouch on Windows Server 2003 and later operating systems.
Note: If you are using a computer as an Alarms database server, install Microsoft SQL Server 2000 with SP3 or later.
InTouch 8.0 with SP2 Installation
Detailed installation instructions are included in the InTouch Installation Guide. It is recommended that you read the InTouch Installation Guide prior to beginning the installation process.
The Microsoft SQL Server key is required in order to install the MS SQL Server. When installing the MS SQL Server, you will be asked to enter the 25 digit key number. The Microsoft SQL Server key number is GJDD4-GMYXW-GQR4C-KT4P9-QDQGB.
InTouch 8.0 with SP2 can be installed on a “clean” system (a system without an existing installed version of InTouch), or it can be installed as an upgrade to a system that already has InTouch 8.0 or InTouch 8.0 SP1 installed.
When upgrading from InTouch 8.0 or InTouch 8.0 SP1 to InTouch 8.0 with SP2, the installation procedure will detect which components have already been installed on your system and will update your system accordingly. Changing the existing installed components (adding/removing components) during the upgrade is not recommended.
Upgrading from InTouch 8.0 to InTouch 8.0 with SP2 may require a reboot if the Microsoft MDAC version currently installed on the system is not up to the prerequisite version level required by InTouch 8.0 with SP2. InTouch 8.0 with SP2 requires, as a minimum, MDAC 2.7 SP1 for Windows 2000 and Windows XP Professional, and MDAC 2.8 for Windows Server 2003. MDAC version is automatically checked during installation procedure.
Upgrading from InTouch 7.11 to InTouch 8.0, InTouch 8.0 SP1, or InTouch 8.0 with SP2 requires that InTouch 7.11 be uninstalled first before the new version can be installed.
Install InTouch Terminal Services on a stand-alone server. We strongly recommend that you not install InTouch Terminal Services on any computer that also acts as a database server (such as IndustrialSQL Server), RAS server or PPTP server.
InTouch and InTouch Terminal Services are not supported and should not be installed on a system that is configured to be a domain controller. InTouch Terminal Services is designed to perform like Windows 2000 Professional at the end-user level and it will not assign top priority to critical domain-level processes. Installing InTouch Terminal Services on any of these servers can significantly degrade performance.
Important Note: If you have to copy the whole InTouch CD to a folder on your hard drive first and then run the installation from this folder, the full path name of this folder should not have a blank space in it. This does not affect users installing InTouch directly from the CD.
Although InTouch can be run by Limited Users, certain features and operations will not be supported for Limited Users. We recommend that users who configure InTouch applications have Power User privileges. The following operations are not supported for Limited Users:
Installing or uninstalling Wizards and ActiveX controls.
Configuring node properties (Limited Users will not be permitted to access Node Properties in the Application Manager).
Converting 16 bit applications created in InTouch 5.6a.
Opening applications created by other users.
Using the license utility.
Using SPCPro features.
Using the Alarm Purge-Archive utility.
Using the Alarm DB Restore utility.
Using the AlarmSuite History Migration utility.
Changing the Alarm DB Logger settings.
Running InTouch WindowViewer as a service on Tablet PCs:
InTouch WindowViewer running as a service is not supported on Tablet PC environments.
Tablet PC Digital Pen Usage - L00018132:
When using the digital pen on a Tablet PC, clicking the digital pen on a direct/reverse action discrete value push button or a momentary push button wizard may not change the value of the tag. This is because the tablet operating system treats "press and hold" as if the user is right-clicking on the object. To address this issue, the user should turn off the "press and hold for right click" at the operating system level. To do so, open Control Panel. Select "Tablet and Pen Settings". Select the "Pen Options" tab from the Tablet and Pen Settings dialog. Select the "Press and hold" pen action and click on "Settings". Uncheck the "Enable press and hold for right click" checkbox.
Porting Applications to Tablet PCs – L00018531:
If a user develops an application using Microsoft Windows 2000 and ports the application to Windows XP Tablet PC Edition, some portions of the application window may not be visible even if the same resolution is used.
To address this issue, users should use the Windows classic theme instead of the XP theme on the Tablet PC.
Tablet PC - Transparency and Color Settings for the Pen and Highlighter – L00018471
Images that are annotated in the Annotate Layout dialog box, which are saved or emailed, do not have the proper transparency settings or color for the pen and highlighter.
Tablet PC - 16 Pen Trend configuration panel does not correctly accept input from the pen input panel – L00018502:
If the user creates an InTouch application and adds a 16-pen trend to a window, configures the trend in WindowMaker, clicks on one of the input fields in the grid list of the 16 pens in WindowViewer, then attempts to input text or numbers in the pen input panel, the entry does not display correctly in the text box. To address this issue, users can use the on-screen keyboard instead of the pen input panel to enter text and numbers when using the 16-pen trend.
Alarm Logger – L00018587:
The Alarm Logger skips alarm records if the master record is not present in the database. The Alarm Logger also skips sub-state change alarm records if the master record (equivalent ALM record) is not present in the database.
L00018137:
The use of commas in the Alarm Comment field for InTouch alarm tagnames is not supported.
L00018367:
The Alarm DB View control will not reconnect to the database if the network connection fails, then is restored. To re-establish the network connection, close the window containing the Alarm DB View control, then reopen it.
L00018184:
Converting an application developed using InTouch 7.1 P08, InTouch 7.11 P03, or InTouch 7.11 P04 to InTouch 8.0 changes the dimensions of the Symbol Factory 3-D pipes. To correct this issue:
1. Before converting the application, add the setting CallWizardSize=1 to the INTOUCH.INI file.
2. Open the application in WindowMaker, and allow WindowMaker to convert the application.
3. [IMPORTANT] Double-click each 3D pipe object in the application. The pipe will be adjusted to the correct size, although the status bar will still indicate the incorrect size.
4. Save and close all application windows.
When you reopen the window, you will find the 3D pipe is the correct size, and the status bar shows W,H as 400,50 on 1024x768 resolution, 312,39 on 800x600 resolution.
L00018348:
For InTouch applications on tablet PCs, the Undo function on the Edit menu cannot be used to undo deletions made using the eraser.
Guide/Chapter / Heading / Page Number |
Existing Text |
Issue / Comments |
Wonderware
FactorySuite InTouch Alarm Deployment Guide, Chapter 3, Terminal Services
Alarm Support, p. 100
|
The Distributed Alarm System is capable of distinguishing alarms coming from different Terminal Sessions and different instances of the same application. |
The
existing text is incorrect. The note stating “Alarm Providers are not
supported on Terminal Sessions. They are only supported on the Terminal
Console” is correct.
|
Wonderware
® FactorySuite™ SQL Access Manager User’s Guide, Chapter 5, p. 44,
Troubleshooting Functions.
|
N/A
|
The
result code -6 for SQL Access is not documented.
For the result code -6, the error message is "Invalid statement ID." The error can occur because a SQL Access function is called with an invalid statement ID as a parameter. A possible cause is that the statement ID returned from SQLPrepareStatement is corrupt (e.g., by a script) before it is used in a subsequent SQL Access function such as SQLExecute, SQLInsertExecute, SQLInsertEnd, SQLSetParam{Type}, SQLClearParam, or SQLClearStatement. |
L00006838:
Check boxes for disabling the vertical and horizontal scrollbars in the distributed alarm display are not available.
L00007809:
The keypad dialog box displays an incorrect title after calling the ChangePassword() function. "Enter new password" is displayed even if the user is entering an old password.
L00010562:
DBload load fails with this message in the Wwlogger: xx Line cannot be changed this points to a read only it is using a read/write.
L00010863:
When purging and/or archiving a large database (approx 300,000 records) a memory leak occurs and the computer memory usage reaches 100% of capacity.
L00010999:
If the user sets (.AlarmUserDefStr), $system.AlarmUserDefStr=$Operator in a data change script, the 'OperatorName' column and the 'User3' column in alarmDetails database are not identical.
L00011488:
When using the HDMerge ActiveX object to import a CSV file into InTouch historical data, progress is slow and the process will freeze up.
L00011533:
If the user has a window that is larger the screen resolution and moves the mouse over part of an object that is outside the viewable area, the halo around the object is visible after the mouse moves away.
L00011635:
Users cannot set the Alarm Buffer Size in the Distributed Alarm Object.
L00011648:
The InTouch print to text file does not wrap around and line break correctly.
L00011659:
The AlarmComment field for Message tags is missing for DBDump/DBLoad.
L00011719:
The DialogValueEntry() function does not display properly in a multi monitor environment.
L00011721:
The DialogStringEntry() function does not display properly in a multi monitor environment.
L00011757:
16 pen trend loses data when another window is open. When the 16 pen trend is used in the Real Time configuration, data disappears when a window is opened over the trend and then closed. The trend appears to refresh but with a lot of data missing.
L00011790:
SQLInsertPrepare and SQLInsertExecute are not inserting NULL into database. The following error message is displayed "-1: Type mismatch. >>Error >>Executing SQLInsertExecute.”
L00011825:
The SQLSetParamChar() function is not working properly in the upgraded version of SQL Access.
L00011927:
If the user adds a 'query favorite' to the Distributed Alarm Object, then sort by name, the new query is displayed at the top. When the user closes the window, reopens it, and right-click the object to view the query favorites, the query favorite is not displayed and there are 2 entries for the default query.
L00012046:
Distributed History queries to InSQL v8.0 are not forming properly when used with international operating systems
L00012230:
WindowViewer crashes if 16 Pen Trend is used without any tags assigned to the pens.
L00012271:
The modal property for scripts does not work if there is an error during validation
L00012354:
The Alarm Printer prints "alarm state" information (UNACK_RTN) for event records.
L00012369:
In WindowMaker, if the user selects an item in the window by clicking the mouse, the object moves up one pixel and over one pixel.
L00012425:
AlarmDBView Control takes a long time to be populated with data if the database contains a large number of records.
L00012439:
If the user creates a new application with certain Japanese characters in the directory path, the directory is created but the application cannot be opened.
L00012497:
Dialogvalueentry() causes InTouch to hang when used in a button with other scripts.
L00012500:
The tab order in the cross-reference utility dialog box is not in the proper sequence.
L00012535:
If the user converts an InTouch application containing InTrack ActiveX controls, but does not have InTrack installed, WindowMaker crashes.
L00012554:
An abnormality occurs in interlocking value entries based on specified tag limits.
L00012646:
The Alt+Q accelerator key in the cross-reference search criteria dialog box is assigned to both the "checkbox usage in QuickFunction" and the radio button "Quick Functions."
L00012770:
On the MicrosoftÒ WindowsÒ 2000 operating system with SP2 or SP3, WindowMaker takes a long time to save windows to a file server/network.
L00012839:
The "Analog Tagname Display with Tagname Text" wizard does not display the tagname and value properly if the tagname contains "0".
L00012979:
If the user tries to change the customized palette color for Unack Alarm the system hangs.
L00013425:
The WWHeap error occurs when converting a script because the Access Names dialog box is modalless.
L00013652:
If the tag limit exceeds the allowed number of tags (61405) and the user creates a super tag instance, a message box appears indicating that the tag limits has been exceeded. The message box is not modal so the user can click outside the box and exit from the Tagname Dictionary. If the user does this, it is not possible to close WindowMaker without restarting the computer.
L00013664:
If the user enters an invalid password using the ChangePassword() script function, the resulting error message is in English in localized versions of InTouch.
L00013834:
The X or Y location of the window changes if the user reduces the Width or Height of window manually.
L00013856:
When entering an invalid floating point value (e.g. entering a comma instead of decimal point), the resulting error message box window is not modal and the application can only be closed using Task Manager.
L00014081:
Hexadecimal numbers are treated as tags in script editing when they are concatenated with a close parenthesis ")" without spaces [Example: ) (0x010 + 0x0A0)].
L00014207:
The Wwheap limitation process registered entries is too low.
L00014244:
If the user places invalid data in the Interval or Duration tags has HistData create a file with that information, it will generate a file with the same entry repeated. This causes the HistData file to grow until the computer fails because the hard is out of space.
L00014270:
The first event that occurs when the SQL Server is disconnected (i.e. MSSQLServer service stopped) is not logged in the alarm database.
L00014399:
The error message, "cannot open tagname.x" is displayed after importing windows containing clock Wizards, which have been previously exported.
L00014607:
Using InTouch 7.11 Patch 05a, a problem occurs when using a Custom Wizard with an Analog Colors Change Animation Link.
L00014652:
If the user has a memory real tag or an IOReal tag and sets the min/max EU or min/max values, there are rounding differences between the two.
L00014653:
The 16-Pen Trend does not repaint correctly when locking up window (Ctrl+Alt+Del).
L00014830:
A new InTouch function called "DateTimeGMT()" has been added to InTouch 8.0 with SP2. This function is listed under the "Misc.." category of InTouch functions. This function does not accept any input parameters. It will return the GMT time since 1/1/1970 in fractions of days. This function must be called in a script as follows:
realValue = DateTimeGMT();
The "realValue" can be a real tag or a local variable in a script.
L00015072:
DialogValueEntry allows the user to enter a null value and then translates the value to zero.
L00015121:
If changes to the tagname value are smaller than update rate, trend displays a min/max value box until the tagname value changes again.
L00015140:
Wizard Generator Wizards lose animation links.
L00015315:
The Purge/Archive utility fails on a partial purge of the database.
L00015361:
On the visibility animation link and discrete value display animation link, the placement of the ON and OFF options is not consistent with that on other animation links.
L00015540:
The while loop of a condition script does not execute with a frequency based on the timer interval.
The "Timer" for InTouch runtime depends on the Tick Interval setting defined for WindowViewer. The value for "Tick Interval" defaults to 100 msec and can be configured during design time using WindowViewer configuration dialog box. To set the basic time interval, click the Special menu, point to Configure, click WindowViewer and set the Tick Interval. On Windows 9x systems, the lower limit is 55 msec. On Windows NT and Windows 2000, the lower limit is 10 msec. This sets the value for TimerTickInterval in the INI file. We recommend setting the Tick Interval no higher than 50 msec for a script that is supposed to come up every 100 msec.
L00015569:
If the user makes minor window changes and deletes a tag in an application, then opens the application, WindowViewer crashes.
L00015617:
16 pen trend crashes in tdatasrc.exe.
L00015746:
Timestamps of IO tags are not updated properly if the change is triggered locally via user input or if the tag is poked from other source. This causes data to be viewed as 'Out of date' by InSQL.
L00015819:
The Purge/Archive utility fails to shrink the database after purge operation.
L00015936:
If an ActiveX Control is active, a frame is shown around the control.
L00015939:
When using update use counts the WindowMaker crashes with a Dr. Watson error.
L00015942:
When the user switches between WindowMaker and WindowViewer, peaks appear in the polygons.
L00015983:
16-pen trend shows an extra, long vertical line where there should just be a single point and the pen thickness increases at the left of the screen. This happens when data moves across the screen.
L00016238:
The TRUNC function does not truncate real numbers correctly.
L00016389:
Clicking the Cancel button will undo a visibility animation link.
L00016440:
Error messages are logged when user pastes a 16-pen trend scooter onto a window and when a window containing a 16-pen trend scooter is opened.
L00011866:
Operating system-based security account passwords expire without warning the user. GetAccountStatus was added and it returns the number of days before password expiration.
L00011946:
When using the Alarm Hot Backup system, some alarms are automatically acknowledged under certain circumstances.
L00012212:
Changing the time span for a real time trend while WindowViewer is running results in the assertion error: Memsmplr.c Line 991 (711) or Line 396 (8.0) Sample.c Line 379
L00012261:
WindowMaker crashes when opening the Tagname Dictionary after an alarm group is deleted.
L00012438:
When a Client is querying a remote Alarm Provider (\\Node\InTouch!$System) and the Provider is shut down or disconnected, then restarted, the following error message is displayed: “upERR lpKeyToRemove not found in AlmKeyIndex::RemoveKey AND !ERR dwPosition [24, max=22] out of range.”
L00012978:
InTouch 8.0 security with OS authentication does not work as it is documented in page 201 of Users Guide
L00013043:
The poke command is not working with wwClient script.
L00013223:
InTouch modifies the IO Tag Quality when raw min/max values are exceeded.
L00013297:
Using InTouch 8.0 with OS security on Windows XP Pro SP1, if a domain user has been assigned to both a domain group and a local group, the logon either does not work (with Logon failed message) or gives the wrong access level for the user.
L00013353:
SQLSetParamChar does not work if more than one Char parameter is set.
L00013422:
The InTouch 8.0 Alarm Printer date and time are incorrect.
L00013432:
If a user has a tag set as Read Only and makes an assignment to one of the dotfields, the user cannot change the tag from Read Only to Read Write.
L00013441:
The user is not able to query data from InSQL that was generated / stored from the Industrial Application Server in the InTouch Trend Object.
L00013561:
WindowViewer stops updating time stamp for I/O Tags after switching the access name via IOSetAccessName.
L00013565:
The File/Print utility in WindowMaker is not properly checking the usage of tags in the application startup and shutdown script.
L00013965:
$DateTime is calculated based on the local time, not based on GMT.
L00015043:
The Distributed Alarm buffer in InTouch 8.0 does not hold the number of historical alarm records that is indicated.
L00015083:
HDmerge.exe and Histmerge.OCX do not work
L00015088:
In InTouch 8.0, changes to SuperTags are not reflected in NEWTAGS.TAG file for Delta-Reimport into an InSQL Server.
L00015443:
The font on the Historical Trend Legend wizard is resized when the window is opened in WindowMaker. This occurs for standard fonts like Arial, Times New Roman and Courier.
L00015533:
HDMerge merges an incorrect time stamp if the csv file was modified by using the Microsoft Office 2000 version of Excel.
L00015536:
The progress bars in Histmerge.OCX do not work correctly.
L00015537:
Message tags marked as log events are truncated to 31 characters when logged to the WWALMDB database by the Alarm DB Logger.
L00015558:
In InTouch 8.0, Distributed History queries to InSQL 8.0 are not forming properly when used with international operating systems (specifically German).
L00015609:
The default DB Dump does not extract tagnames in alphabetical order.
L00015935:
The user cannot control whether or not InTouch creates a shared license folder.
L00017129:
The InTouch print to text file needs to be improved. The line break does not always work, the text sometimes contains invalid characters and the text wrap around text does not work, which may cause some information to be cut off.
L00017468:
The original design does not provide a way to start the Alarm DB Purge-Archive utility in activated mode.
Upon startup of the utility, the user should check the [InTouch] section in the win.ini file. If AlarmDBPurgeArchiveActivated=1 is present, then start in activated mode. Otherwise, the default behavior is followed.
L00017811:
The handling of time stamping on InTouch I/O tags has been changed. Previously, the timestamp was updated on an I/O tag only when data was received from the source. Now, the timestamp is also updated if the data is changed on the local InTouch.
Tablet PC Support
InTouch 8.0 with SP2 enables users to work with InTouch on Tablet PCs. Tablet PCs enable users to use the tablet display like a writing tablet, while retaining the ability to use the keyboard and/or mouse. Users can also control the Tablet PC and Windows XP–compatible applications using the tablet pen. Tablet PCs are not supported using InTouch Terminal Services.
One can also use the Tablet PC digital pen to perform commands instead of the mouse. The table below shows examples of common actions performed with the mouse as well as the corresponding default settings for actions using the digital pen. For more information on Tablet PC functionality, refer to the Tablet PC documentation.
|
Mouse |
Digital Pen |
|
Point |
Point |
|
Click |
Tap |
|
Double-click |
Double-tap |
|
Right-click |
Tap and hold |
|
Click and drag |
Drag |
The following features have been added to InTouch 8.0 with SP2 in order to provide support for Tablet PCs:
Pen Input Panel
The InTouch WindowViewer displays edit boxes when the user clicks touch links of Analog or Message types. In addition to these edit boxes, WindowViewer now displays the Pen Input Panel to facilitate data entry using the digital pen. Note that the Pen Input Panel will only be displayed if WindowViewer is running on a Tablet PC.
The Pen Input Panel is displayed only when the Keypad option of the touch link is set to "No."
The default input method for the Pen Input Panel is handwriting. However, users can switch between handwriting and keyboard input methods using buttons on the user interface.
AnnotateLayout Script Function
When AnnotateLayout is called, the Annotate Layout dialog box appears. This dialog box has the following functionality:
· Captures the screen image of WindowViewer at the time this dialog box is displayed
· Allows for annotation on the screen capture using the tool bar and menu items.
· Allows the image and the annotation to be saved as a GIF or JPEG file.
· Allows the image and the annotation to be printed (if a printer is configured).
· Allows the image and the annotation to be sent as an attachment via e-mail (if SMTP is configured).
The Annotate Layout dialog box contains a toolbar and menu items and shows the InTouch WindowViewer screen capture in its client area. The dialog box has a Close button on the caption bar, but does not have minimize or maximize buttons.
Annotate Layout Toolbar
The toolbar includes the Save, E-Mail, Print, Cut, Copy, Paste, Pen, Highlighter, Eraser and Lasso functions. The following table explains the functions of the toolbar commands:
|
Command |
Functionality |
|
Save |
Saves the image and annotation as a GIF or JPEG file. When the user clicks Save, the Save an Image File dialog box appears. The default directory is the current user’s “My Documents.” By default, the image is saved as a JPEG file. |
|
|
The E-Mail functionality in the Annotate Layout dialog box uses SMTP (Simple Mail Transfer Protocol). |
|
|
Invokes the standard “Print” dialog box and allows the user to print the annotated image to the selected printer. If a printer has not been configured, this toolbar function will not be available. |
|
Cut |
Cuts the annotation selected using the lasso. Accelerator key is Ctrl + X. |
|
Copy |
Copies the annotation selected using the lasso. Accelerator key is Ctrl + C. |
|
Paste |
if any previously cut or copied annotations are available in the clipboard, this function allows the user to paste it in the current window. Accelerator key is Ctrl + V. |
|
Pen |
Enables the user to annotate the screen capture in the Annotate Layout dialog box. Expands to the “Color”, “Size”, “Tip” and “Transparency” options. Click Color to choose the pen color. The default is Red. Click Size to choose the thickness of the pen line. The options are 1pt to 5 pt thickness and the default is 1pt. Click Tip to expand to “Ball” and “Rectangle.” The default is “Ball.” A check mark on the left side of the menu indicates the current selection. Click Transparency to select the transparency. The default is 0%. |
|
Highlighter |
Enables the user to highlight annotations on the screen capture in the Annotate Layout dialog box. Expands to the Color and Transparency options. Click Color to select the highlighter color. The default color is yellow. Click Transparency to select the transparency. The default setting is 50%. |
|
Eraser |
Enables the user to erase annotations on the screen capture in the Annotate Layout dialog box. Expands to the Mode and Size options. Click Mode to select the Stroke or Point options. The default is Point. A check mark on the left side of the menu indicates the current selection. Click Size to select either Small, Medium or Large. The default eraser size is Medium. A check mark on the left side of the menu indicates the current selection. |
|
Lasso |
The Lasso is a drawing tool that allows users to select annotations on the screen capture to Cut or Copy. |
Annotate Layout Menus
The Annotate Layout dialog box includes the following menus with the following functions:
File menu
Save (Ctrl + S) – Saves the current screen capture.
E-Mail (Ctrl + M) – Invokes the New Message dialog box.
Print (Ctrl + P) – Invokes the Print dialog box and allows the user to select a printer.
Exit (Alt + F4) – Exits the Annotate Layout dialog box.
Edit menu
Undo (Ctrl + Z) – Negates the most recent annotation.
Redo (Ctrl + Y) – Reapplies the most recently negated annotation.
Clear – Expands to the following options:
All - Clears all annotations on the screen capture in the Annotate Layout dialog box.
Selection - Clears the annotations selected using the Lasso.
Cut (Ctrl + X) – Cuts the annotation selected using the lasso.
Copy (Ctrl + C) - Copies the annotation selected using the lasso.
Paste (Ctrl + V) – Pastes the cut or copied data into the current window.
E-Mail Configuration – Allows the user to set up the SMTP server name.
Tools menu
Pen - Enables the user to configure the pen. Expands to the “Color”, “Size”, “Tip” and “Transparency” options.
Click Color to choose the pen color. The default is Red.
Click Size to choose the thickness of the pen line. The options are 1pt to 5 pt thickness and the default is 1pt.
Click Tip to expand to “Ball” and “Rectangle.” The default is “Ball.” A check mark on the left side of the menu indicates the current selection.
Click Transparency to select the transparency. The default is 0%.
Highlighter – Allows the user to select Color and Transparency options for the highlighter.
Eraser – Allows the user to select Mode and Size options for the eraser.
Lasso – Allows the user to select annotations on the screen capture to Cut or Copy.
Restore Defaults - Resets all options for the tools such as Pen, Eraser and Highlighter, to their defaults.
Help menu
About – Displays the About dialog box.
All the toolbar and Tools menu settings are persisted on a per user basis. When the setting dialog box is displayed, the user’s current pen/highlighter/eraser options are the last settings used and not the default settings.
Portrait/Landscape Orientation
Some tablet PCs can be used as either a tablet PC or a laptop PC. When switching from one configuration to another, the orientation by default is switched. For example, if the tablet PC running in laptop configuration is switched to tablet configuration, the screen orientation will be switched from landscape (1024x768) to portrait (768x1024).
If the tablet PC is running in tablet configuration, and WindowViewer is configured to dynamically change the application resolution to the screen resolution, an application developed in landscape orientation will be automatically scaled to fit the portrait orientation when opened in WindowViewer. If WindowViewer is not configured to dynamically change the application resolution, however, the landscape application will be displayed unscaled. In this case, some InTouch windows may be truncated.
Alarm Viewer ActiveX Control Display
Users can configure unacknowledged (UNACK) alarms to flash in the Alarm Viewer control. A property named "Flash Unack Alarms" is provided as a check box. UNACK alarms will flash only when this check box is selected. By default, this check box is not selected. When the user selects Flash Unack Alarms, only UNACK alarms will flash. UNACK_RTN alarms will not flash.
Five new properties have been added to the Alarm Viewer
ActiveX control to enable the alarm flashing functionality. The five new
properties are explained below:
