In D11144#211109, @zmike wrote:

I went full stupid and only needed like 70% stupid

I wonder if 70% stupid makes you less stupid or more intelligent? :P

Anyways, I liked the variable thisisreallystupid instantly.

In D11144#211181, @CHAN wrote:

@zmike Thank you.

Please explain more detail about this patch.

Which part can I help with? The goal is to resolve (in a hasty manner) the problems that the existing gesture callback hooks (e.g., _efl_canvas_gesture_manager_callback_add_hook()) have wherein having 2+ user callbacks added for a gesture on an object (as in D11145) will process the same input events 2+ times and break the recognizer. I tried to explain this in the commit log, but maybe I could have worded it more clearly somehow.

@zmike Thank you for the details.

I understand but if user register another widget's changed callback twice, for example spin_button, that callback will be called twice.

It doesn't seem to matter if the user registers the gesture callback more than once and recognizes it more than once.

Hm that's an interesting point. In that case, I suppose I'd expect the events to be emitted n times, but the gesture recognizer must only be run 1 time per gesture. I can fix this.

Ignore everything I said before, working on too little sleep.

@zmike do i have to see this commit more?

In D11144#213538, @CHAN wrote:

@zmike do i have to see this commit more?

There shouldn't be an issue having all callbacks triggered? That's something handled by eo, not the gesture manager.