QQuickWindow flushFrameSynchronousEvents: don't hover if nothing dirty

An optimization revising 6f84a09dfbd15aac023580cf06e7b8c24f3b524c
Calling hoverMoveEvent every frame is too inefficient when an item
subclass is actually doing something there.  For example, any
QtQuick-based Wayland compositor needs to notify its client windows
when hover state changes, so calling this method too often would
impose extra work to double-check whether it really changed or not.

Change-Id: I98b40a2083700e7a50820bd13154247444249e59
Reviewed-by: Robin Burchell <robin.burchell@viroteck.net>

0 files changed, 0 insertions, 0 deletions