Page MenuHomePhabricator

efl/gesture: do not emit events for canceled gestures with no state
Needs ReviewPublic

Authored by zmike on Mon, Jan 6, 11:29 AM.



for non-continuing gestures which have been canceled at this point, we must
not emit events in order to avoid sending useless events which serve no
purpose other than to waste cpu cycles

Diff Detail

rEFL core/efl
Lint OK
No Unit Test Coverage
Build Status
Buildable 15446
zmike created this revision.Mon, Jan 6, 11:29 AM
zmike requested review of this revision.Mon, Jan 6, 11:29 AM
bu5hm4n requested changes to this revision.Tue, Jan 7, 3:56 AM

Mhm, not too sure about that. Independend from continues or not, we should tell the user that this gesture is updated,( thinking about using this in scroller, when momentum is canceled, and its "moved" to be a flick, we should tell that to the user...), i am not even sure if its a good idea to have this continue when they are continues ...

This revision now requires changes to proceed.Tue, Jan 7, 3:56 AM
zmike requested review of this revision.Tue, Jan 7, 7:09 AM

No, this is a case where the gesture has no state. It means the gesture was canceled before anything happened, which would result in an update event without any other prior event and with a gesture that has a NONE state, which can never be used for any purpose.

zmike added a subscriber: CHAN.Tue, Jan 7, 7:23 AM

I'd like to get a reply from @CHAN on this

zmike updated this revision to Diff 28125.Mon, Jan 13, 12:11 PM
zmike edited the summary of this revision. (Show Details)


I'm not sure who is able to review gesture code at HQ, but if there is anyone then we can give a week or so for them to have time to check these patches out. Otherwise we will just review and process upstream normally.

CHAN accepted this revision.EditedThu, Jan 16, 8:50 PM

Looks good to me.

Jaehyun_Cho accepted this revision.Thu, Jan 16, 10:19 PM