The entirely new communication capability that ThinView opens for a remote CIMPLICITY user affects how some CimView features perform.
When you configure CimView screens that remote users will access through ThinView, keep the following basics in mind.
The consequences of the user's actions occur on the ThinView server, not at the Windows CE device location. For example, if a file is deleted through ThinView, it is deleted on the ThinView server computer, not on the Windows CE device.
Data is transmitted over lower bandwidth (wireless network) or through a network that is possibly being used by numerous other applications.
Therefore, the configuration decisions you make will increase the effectiveness of the CimView screens being viewed from a remote location.
More specifically, following are some guidelines for CimView features in relation to ThinView.
A ThinView user can perform an ExecuteCommand or scripted action that interacts with the server. A command that, for example deletes a file, can be very useful. However, because the result is on the server, some commands are not useful to the remote user. For example, if you configure an action that opens Microsoft Notepad, Notepad will open on the server. The ThinView user will not see it.
A Print action prints on the server printer. This action is useful if the ThinView user wants a printout for another individual who is at the server location.
An Alarm Viewer that opens a specified CimView screen, when it is pushed, opens the screen on the server, not through the Windows CE device.
An Open Screen action behaves like an Overlay Action through a Windows CE device. It will replace the displayed screen with the selected screen. It does not open another ThinView window.
Note: When you create an Overlay Screen or Open Screen action, enter the name of the screen to overlay in the Screen name field. If no file name is specified and a remote user attempts to trigger the action, ThinView will display an error message.
Right mouse button behavior
Right mouse button actions that are used on the CimView screens are not recognized through ThinView. This means that popup menus do not display and, consequently, a user cannot access other features through those menus. ThinView displays its own on the Windows CE device.
ActiveX controls that ThinView supports include Trend, Alarm Viewer, SPC, CimGraph and Recipes.
Note: You can script some of the features that use menu items and right mouse button features through CimView.
Third party ActiveX controls are not supported. However, they may work, particularly if they do not use separate windows, display dialog boxes or require menu displays.
ThinView supports standard CimView scripts. However dialog boxes from Basic scripts (for example, the MsgBox function) and popup menus are not supported.
A remote user can interact with OLE objects whose primary function is display (e.g. Word or WordArt).
Other OLE objects, such as sound, will open on the server. Someone who is near the server may hear them. The remote user will not.
Because ThinView deals with Viewer capability, it is most efficient to put it on a server that points to both the primary and secondary computer in a redundant pair. However, if you decide to make the primary computer also the ThinView server, you will have to manually reconnect the slave if the master goes down.
Other features to consider
The onscreen keypad, which is called through a command line parameter, /keypad, does not display through ThinView.
The read-only Properties dialog boxes will not display when a remote user double clicks an object.