Vivotek ST3402 Launcher Section 2: User Interface

From EZWatch Wiki

Vivotek ST3402 Launcher Section 2: User Interface

This is the user interface for Launcher:

The main user interface for Launcher is an icon on the system tray.

The popup menu is displayed by clicking on the right or left buttons on the mouse. The menu items are listed below:

1. Lock Launcher – When this item is selected, Launcher will enter Lock mode. In Lock mode, whenever the user wants to invoke the menu, a dialog asking for username and password appears. The interface for this dialog is covered in the previous section.

2. Tools – This contains utilities; currently only change password and user management are implemented.

  I. Change password:
     The tool can be used to change the password of the login user. 
     Below is the change password screen:
  
  
   
  II. User management:
      Fig. 2-5 shows the tool of user management. The tool can be used to add, modify or delete user. 
      The maximum available user is 30 and the number of available user will be shown in “Resource” field. 
      As shown in Fig. 2-6, when you want to add a new user, you should specify user name, password
      and user’s group for the user. You can modify user’s status in Modify Status window.
 
  

  ATTENTION: The tool can only be invoked by users of root group. The default root (root / admin) cannot be removed 
  and the user could remove the other users of root group.

Functionalities may be disabled according to the login user’s group. The following table represents the privilege of each group in Launcher.

3. Monitor start up mode – The option decides the program type of Monitor that is described in section 3 after Window boot up. There are three kinds of types:

Service: Do not Autorun – The Monitor will be run as a service but it will not be invoked automatically after Window boot up. Manual startup is needed.

Service: Autorun – The Monitor will be run as a service procedure and it will be invoked after Window boot up automatically without login. Recording procedure will be also invoked if proper schedule is configured. More detail about scheduler in Monitor.

Non-Service – The Monitor will be run as a normal procedure (non-service).

User can invoke Monitor by using the interface provided by Launcher.

NOTE: When Monitor runs as service procedure, it will work in background after closing (click on the close button in Monitor). It means that the recording procedure will be continued and user does not need to worry about missing media data that you like to record.

4. Monitor – This starts up the Monitor. If the Monitor is already running, move the focus to it.

5. Playback – This starts up Playback. If Playback is already running, move the focus to it.

6. Exit – This ends Launcher. If the user chooses this option, a message box will pop up to confirm whether the user really wants to exit. It warns the user that exiting Launcher will also close Monitor and Playback.