Use separated Core::QueueEvent & ProcessEvents methods (instead of SendEvent)
authorPaul Wisbey <p.wisbey@samsung.com>
Thu, 6 Feb 2014 18:39:59 +0000 (18:39 +0000)
committerPaul Wisbey <p.wisbey@samsung.com>
Mon, 3 Mar 2014 18:59:38 +0000 (18:59 +0000)
commit6030e70386219467a6fb42613e1835636eb1790e
tree4bf561f8d063ca6b1ca9778c57e262668220d869
parented98138d6600414bb5092a2fb5e8f542a4bacb0e
Use separated Core::QueueEvent & ProcessEvents methods (instead of SendEvent)

[Issue#]   N/A
[Problem]  Adaptor is calling SendEvent multiple times for each raw touch event,
causing extra effort with message queuing, size negotiation etc.
[Cause]    SendEvent was doing two different jobs i.e. queueing & processing.
[Solution] Use the separated QueueEvent & ProcessEvents methods
adaptors/tizen/internal/common/events/event-handler.cpp
adaptors/tizen/internal/common/events/long-press-gesture-detector.cpp
adaptors/tizen/internal/common/events/pan-gesture-detector.cpp
adaptors/tizen/internal/common/events/pinch-gesture-detector.cpp
adaptors/tizen/internal/common/events/tap-gesture-detector.cpp