User Details
- User Since
- Aug 24 2014, 6:05 PM (341 w, 14 h)
- Availability
- Available
Feb 5 2017
@devilhorns - Thank you for letting me know. :)
If those patches are ready to share in dev branch (not master branch), I am happy to run tests in enlightenment.
Jan 26 2017
This task is about identification of event source device. I had a interest in this issue and tried to contribute. (refer to.. https://phab.enlightenment.org/D3860)
IMHO, we should fill 'dev' variable in events(Ecore_Event_XXX/Evas_Event_XXX) in drm backend, similar to wayland backend. Then, enlightenment could distinguish source devices from events and deal with that.
Do you agree on this? Shall I try this issue? Please let me know you guys ideas.
Thanks
Jan 25 2017
Oct 24 2016
Glad to hear from you. I'll revise this patch and update soon.
Thanks,
Sep 18 2016
ping?
Jul 29 2016
Please refer all kind comments at https://phab.enlightenment.org/D4179.
Jul 27 2016
Thanks for all your comments.
I had trouble with cute arcanist.. :(
rebased again.. sorry..
revised and rebased.
Thanks,
Jul 21 2016
Dear ManMower,
I revised according to devilhorns comment.
Thanks,
Jul 20 2016
Jun 7 2016
Dear jpeg,
Good to hear that. I knew you have been working on EO-ifying devices and events. I will check out Efl.Input.Device first.
Thanks~
May 3 2016
Hi,
It's been a month since I made this patch.
I just wonder if this patch needs to be rebased or changed or abandoned.
Or... would you recommend to split this patch into several patches(ecore_device/ecore_drm/ecore_input_evas)?
Thanks for your comments in advance. :)
Thanks, ManMower.
I examined weston-simple-touch client as the way that you mentioned.
Mouse_Binding should work with mouse devices, not touch devices.
So I added check for mouse device when converting mouse event to e_binding_event_mouse_XXX.
Apr 19 2016
rebased this patch.
add comments explaining why sending wl_touch events with "zero id"
Sorry for replying late, Derek.
As you can see, my implementation is very simple.
If event source of Evas_Event_Mouse_XXX is a touch device, we send down/up/motion events using wl_touch, not wl_pointer.
The same job about Ecore_Event_Key is already done.
https://git.enlightenment.org/core/efl.git/commit/?id=0ef41604e88b8a8224818824217ebc09c93789d5
Now, we ensure that all fields in Ecore_Event_XXX(Mouse/Key) will be properly initialized.
Apr 6 2016
need to include <Ecore.h> in Ecore_Input.h
Apr 5 2016
I think this patch are completely updated.
Please let me know your opinion of this commit.
restore previous diff I lost when rebasing..
rebase on top of upstream
revised according to zmike's comments.
I greatly appreciate your comments that helped improve this patch.
Apr 4 2016
revised according to zmike's comment.
Thanks.
Apr 3 2016
Ecore_Device is the Ecore-level Device infomation similar to Evas_Device.
Both are used for identification of source device where the event came from.
Ecore_Device has the string member named identifier which should be unique
distingusing input devices.
For now, the sys name of device provided by udes is used. ex)/dev/input/event2
Apr 1 2016
Feb 14 2016
Feb 2 2016
Jan 27 2016
ignored po files.. Please review this patch, again. :)
modified code in _e_comp_wl_cursor_reload()
Forget about po files.. my mistakes..
Restore po files.. ;)
Removed po files
I revised according to zmike comments. Please review again. :)
Thanks,
Jan 13 2016
Thanks, ManMower.
I created new revision according your comment.
Please refer to https://phab.enlightenment.org/D3555
Jan 11 2016
Jan 7 2016
Dec 22 2015
Dec 14 2015
Dec 10 2015
Updated again. :)
I revised according to devilhorns comment. Please review again. :)