Classes and methods inside classes are already sorted alphabetically in C docs:
https://www.enlightenment.org/develop/api/efl/object
and in C# docs:
https://enlightenment.github.io/www-content/gh-pages/api/csharp/api/Efl.Object.html
so don't worry about me.

This should only affect the C implementation code. We should likely alphabetize any doc generation (cc @segfaultxavi) so that we get consistent docs generated regardless of eo file ordering.

Even if this pays off, i dont know if its really worth it doing that, as the reordering of .eo files seems quite a bit random. Do we really want that ? I will just put the revision here so we can discuss it, maybe we need a better way to do this. (This is also a heavy platform specific depending topic)

rebase & update the complete stack to work arround issues

fixes & rebase

this is wrong.

No more questions, Your Honor.

naming fixes

More fixes and progress

Except for the minor cosmetic of the .h file name not matching the function name, I am good with this. You might want to add a _unregister function as some of the register could be done in a module and disappear at any point.

Unfortunately we don't have a way to detect it with the current infrastructure because the device will be 0 in the case of pointer events when it should probably be -1.

I somehow still do not like that we sent a MOVE before the DOWN event of the first finger, but not for the second finger, that feels absolutly inconsistant. IMO we either do not have move before multi,down and down, or we have it for both, having a different event flow based on if we are multi or not does not make sense. The normal event flow is: in;move;down for multi it would be in;down; that is weird,.

device is 0 on the eel that has ECORE_INPUT_DOWN...

IGNORE ME

Yea remove L709, idk what I was thinking there.

That does not fix the issue... the move event is still sent when a second point is downed .

fix impl

fix api names

Just answer these questions so I can update the docs, thx!

fixes & more docs

phab - behave!

@felipealmeida
please check this and give us your opinion how to go.

fix typo

There are many patches related to gesture. (D11052, D11053, ...)
Therefore, to avoid conflict to the above patches, this patch should not be merged until either those patches are merged or abandoned.

Do not merge yet as this implement need to be discussed in right way.

forgotten changes

update

more changes

Some more review.

Apply planned changes.

add eina_value implementation

rebase

This is for now just a draft, more conversions are missing, and i think we should be able to pass a content with a type as Eina_Value. However, i think feedback here could be of interest.