Post by leiwang on Apr 20, 2017 1:20:09 GMT
When calling HoverMouse, we can see the mouse hovers and then disappears, which is normal. There is an optional parameter 'HoverTime', which tell us how long the mouse will hover on the specified location. By default, the mouse will hover 2000 milliseconds and move away, if we want the mouse stay there longer then we need to give a larger number; if we want the mouse stay there for ever, we should give number -1, defined by TIMEOUT_HOVERMOUSE_STAY_FOREVER
-- Explanations and Notes from Carl --
I just want to clarify a piece of information here. When using our SAFS and/or SeleniumPlus implementations for HoverMouse, the mouse pointer disappearing is actually a historically intended feature. The mouse is hovered, and then quickly moved away—usually off screen. The idea here was that when you want to hover the mouse over an area and see something--like a tooltip--you then don’t want the mouse pointer to be in the way of seeing or snapshotting the item. So, we moved the mouse away so that an image capture or similar activity does not capture the mouse pointer.
It is important to note that the previous implementation of HoverMouse needs to be retained for the missing parameter 'HoverTime', and any parameter greater than or equal to 0. That is, the mouse must be moved, hovered at the location, and then moved away from the location--usually off screen. At no time should the mouse remain at the hover point longer than the requested timeout value--unless, of course, that timeout value is -1. I believe the implementation details and examples imply that, but I wanted to make sure everyone knows that the mouse "disappearing" is actually expected behavior for the HoverMouse command when using the default timeout or any timeout value greater than -1.
---------------------------------------------------------------------
-- Explanations and Notes from Carl --
I just want to clarify a piece of information here. When using our SAFS and/or SeleniumPlus implementations for HoverMouse, the mouse pointer disappearing is actually a historically intended feature. The mouse is hovered, and then quickly moved away—usually off screen. The idea here was that when you want to hover the mouse over an area and see something--like a tooltip--you then don’t want the mouse pointer to be in the way of seeing or snapshotting the item. So, we moved the mouse away so that an image capture or similar activity does not capture the mouse pointer.
It is important to note that the previous implementation of HoverMouse needs to be retained for the missing parameter 'HoverTime', and any parameter greater than or equal to 0. That is, the mouse must be moved, hovered at the location, and then moved away from the location--usually off screen. At no time should the mouse remain at the hover point longer than the requested timeout value--unless, of course, that timeout value is -1. I believe the implementation details and examples imply that, but I wanted to make sure everyone knows that the mouse "disappearing" is actually expected behavior for the HoverMouse command when using the default timeout or any timeout value greater than -1.
---------------------------------------------------------------------
