You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This Problem was first reported over 7 years ago for SWT 4.11 here:
18 Months ago I again verified the Issue still exists on SWT 4.19.
MouseEnter events are sometimes not being fired (or are being lost)
The attached program highlights this.
Traversing as fast as possible with the mouse from left of the window to right of the window fires MouseEnter & MouseExit for all 3 Canvases (see Console).
The 3 Canvases do not overlap, in fact there is a gap between them.
Traversing very fast between, say, the Red & Green Canvases, (only sometimes) the MouseEnter event is not fired. Optically noticable due to the Arrow Cursor.
(normally after entering, the Hand Cursor is shown)
If the mouse is moved very fast it might be that not all intermediate positions are reported by the Mouse or OS. The application then can not decide if the mouse path took the way directly from the old position to the new position or if the mouse was moved around the window. @DanskerDave unless somebody proves that mouse events get lost and contributes a fix this issue will not be handled.
This Problem was first reported over 7 years ago for SWT 4.11 here:
18 Months ago I again verified the Issue still exists on SWT 4.19.
MouseEnter events are sometimes not being fired (or are being lost)
The attached program highlights this.
Traversing as fast as possible with the mouse from left of the window to right of the window fires MouseEnter & MouseExit for all 3 Canvases (see Console).
The 3 Canvases do not overlap, in fact there is a gap between them.
Traversing very fast between, say, the Red & Green Canvases, (only sometimes) the MouseEnter event is not fired. Optically noticable due to the Arrow Cursor.
(normally after entering, the Hand Cursor is shown)
This can also be verified in the Console log.
The MouseExit event seems always to fire.
Attachments:
Example Program highlighting the problem
An updated snippet which prints in console only when there's an error.
Refined Snippet
Revised Snippet to run under SWT v4.11
Environment:
Java Version for Eclipse & Project is 1.8.0_51 64 bit.
Version since
4.11 (& later also verified on 4.19)
The text was updated successfully, but these errors were encountered: