[Tizen] The hover event now starts in the STARTED state when a new actor is encountered. 20/290720/1 accepted/tizen/7.0/unified/20230403.235554 accepted/tizen/7.0/unified/20230404.033728
authorjoogab.yun <joogab.yun@samsung.com>
Mon, 27 Mar 2023 09:56:08 +0000 (18:56 +0900)
committerjoogab.yun <joogab.yun@samsung.com>
Fri, 31 Mar 2023 07:39:29 +0000 (16:39 +0900)
commitb13394993ab3a6847b64bd037cfedf4a82edfbd0
tree7ee069b1f2cc31cd19dfc720dfd3eb8fd83c369d
parent0ff5139db4c9a0603e1d17ccc862a2ca1ca2b42b
[Tizen] The hover event now starts in the STARTED state when a new actor is encountered.

When hover event is registered, only motion comes. You can't know that the hover has started on that actor.
So, when the hover starts on the new actor, set it to STARTED state.

Change-Id: If25595536bce2279529847056ed962c515632165
automated-tests/src/dali/utc-Dali-HoverProcessing.cpp
dali/internal/event/events/hover-event-processor.cpp
dali/public-api/actors/actor.h
dali/public-api/events/hover-event.h