DQA release NR8301v670 NR8201v261

The only difference of v664 from v663 was the fix for the UI error in VAST/iViewer page (iViewer Port).

So all the following remains the same as the release note in NR8301v663 and NR8201v257


Fixed bugs.


1. #20309 Using mouse wheel to do digital zoom in and zoom out that should be smooth in Monitor and History page.
   The cause was the IE does not alway update focus on mouse move. This causes non-response on mouse-wheel when mouse
   is moved. The fix was to force update focus with all mouse movement.
   
    To verify this, connect to FE camera and use mouse wheel.


2. #20313 When VAST controls NR8301's Speed Dome, Speed Dome does not move.
   #20311 When VAST controls NR8201's Speed Dome, Speed Dome does not move.

   For regular non-speeddome PTZ camera, when a PTZ button is clicked, a single PTZ command is issued to camera: 
   HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?move=left. 
   The PTZ camera will response with a left move of a single step.

   With speed dome cameras, we are requested to implement continuous movement. So when a PTZ button is pressed 
   and held, the camera starts and continues moving until the button is released. We implemented with two PTZ 
   commands.
   1) To start movement when button is pressed down, we send the camera  HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?vx=-1&vy=0.
   2) To stop movement when button is release, we send the camera  HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?vx=0&vy=0.

   This is how we implemented in the web interface.

   However, in VAST interface, NR does not receive any requests from VAST when PTZ button is pressed down and hold.
   NR only received a single PTZ request from VAST when the button is released. 
   This is the reason in VIVOTEK USA's case, when PTZ button is clicked in VAST interface, 
   only HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?vx=-1&vy=0 was sent to camera and speed dome never stops.
   We provided a fix by issue HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?vx=0&vy=0 commands right after the first
   commands to request the camera to stop movement. This works for the speed dome VIVOTEK USA provided.

   But DQA's speed dome does not move when we send both HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?vx=-1&vy=0 and
   HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?vx=0&vy=0 commands right away. 
   We have tested that if we add a delay between the commands, the camera does move and then stops. 
   But how long to add the delay may vary for different speed domes and their speed settings. 
   In order to provide a more consistent interface, we went back to use the old PTZ command 
   HTTP://x.x.x.x/cgi-bin/admin/camctrl.cgi?move=left. 
   This way speed domes will behave the same way as other non-speed-dome PTZ cameras, with a move of a single step.

   To verify this, connect a speeddome.

3. #20428 [Android] iViewer can not connect NR8301.
   #20429 [Android] iViewer can not connect NR8201.

   The cause was Android does not send "LiveOnly" and "MaxRec" fields in QryLocs commands. The fix was to add processing to deal 
   with the missing fields. To verify this, connect using Andoid iViewer.

4. [FAE] IE 9 hang on logout.

   The cause was the logout was processed twice, once on logout comnmand and once on IE exit.
   In IE9, IE will hang on the second logout processing. The fix was to add a flag to prevent the second logout.
   To verify this, connect IE9 and click on logout.