path: root/src (follow)
AgeCommit message (Collapse)Author
2016-05-31ecore-evas-drm: Register direct input callback for gl_drm alsoChris Michael
@fix Signed-off-by: Chris Michael <>
2016-05-31elm: Fix build (use efl_ui_image.eo)Jean-Philippe Andre
2016-05-31elm_image: rename the elm_image into efl_ui_image.Ji-Youn Park
2016-05-31Evas: Add proper EO events with info for mouse inputsJean-Philippe Andre
This adds a few classes, in particular Efl.Event and Efl.Event.Point which are used as the event info for all pointer (mouse, multi) call Using an eo object as event info will allow for future extensions really easily. We don't need to expose any of the internals, also a single type can be used for all pointer events. Still TODO: - Keyboard events (urgent) - Axis / Joystick events (needs porting from Tizen) - Gestures support (probably later) - Event feeding from app side (manual feed) Not going to be ported to EO: - Hold API and hold event. Seems barely used. The new APIs are not very much tested at this point, and rely on the old legacy event system. The most important thing right now is to ensure that nothing was broken so far. Unfortunately I can only do this much testing myself... Merge branch 'devs/jpeg/work'
2016-05-31Efl: Rename Efl.Pointer.Event into Efl.Event.PointerJean-Philippe Andre
Also renames two types: Efl.Pointer.Flags and Efl.Event.Flags
2016-05-31Evas events: Fix a crashJean-Philippe Andre
There was an invalid reference used because we changed legacy event type without resetting eo event info. Scenario: scroll + click
2016-05-31Evas events: Propagate event flags between eo and legacyJean-Philippe Andre
If on_hold or on_scroll is set in an eo callback, the subsequent calls to the legacy callbacks will also have this flag set. Inversely the legacy callbacks should affect all subsequent eo callbacks. Note: those are just indicative flags.
2016-05-31Evas events: Add helper functions to read event infoJean-Philippe Andre
This adds simple helpers for double/triple click and on_hold/on_scroll flags.
2016-05-31Evas events: Store position as double onlyJean-Philippe Andre
This splits pixel and subpixel precision by using different methods rather than two different storage values.
2016-05-31Efl event: Remove useless method declarationJean-Philippe Andre
2016-05-31Evas events: Split pointer eventsJean-Philippe Andre
This is going back to the same idea as legacy. We will have events such as: - move - down - up - in - out - wheel - cancel ("new" - very rare) Now the question is whether/how we should divide "multi" events which start from the 2nd finger from standard mouse events. The first multitouch finger should by default look like a mouse event.
2016-05-31Elm win: Forward pointer events from evas to windowJean-Philippe Andre
This will allow applications to listen to those events on the whole window. Necessary since they won't have access to Evas with EO APIs.
2016-05-31Evas events: Add EO APIs for lock & modifiersJean-Philippe Andre
This moves Efl.Pointer.Event back to Evas. Originally I wanted to share this class with Ecore but eventually I didn't need to do so, since only ecore_evas (which depends on evas) really needs access to these. The internal data struct is not moved out of efl (yet?)
2016-05-31Evas events: Replace calls to event feed with internal funcJean-Philippe Andre
2016-05-31Evas events: Pass Efl_Pointer_Event for proxy source eventsJean-Philippe Andre
2016-05-31Evas events: Forward more pointer eventsJean-Philippe Andre
This continues the work started in the previous commit: forward full event info (Efl_Pointer_Event) from evas to the upper layers. This also includes more support for IN and OUT.
2016-05-31evas: send eo pointer events on mouse moveJean-Philippe Andre
This is still VERY experimental and not fully done yet. All other pointer events need to be sent as well. The legacy event system is used as a transportation mechanism, as it is too hard to change the logic. This only adds an extra eo event in case of move. Obviously for performance we might want to listen to callback_add,del but that's an optimization for later. The whole point of sending those pointer events is to carry more information than can be sent over legacy evas events, and unify the events in a common format.
2016-05-31Efl.Pointer.Event: Add dup() method to copy an eventJean-Philippe Andre
2016-05-31ecore_x: Pass in/out through ecore_input_evasJean-Philippe Andre
This whole input system is a massive mess. It looks like spaghetti. Long live the giant flying monster. This commit changes how some events are propagated in X. Before: ecore_x -> evas_event -> evas After: ecore_x -> ecore_input_evas -> ecore_evas -> evas_event -> evas There are still inconsistencies between events and between X and WL, but ecore_evas should be used for all events since it rotates the inputs.
2016-05-31evas_events: Propagate more eo pointer eventsJean-Philippe Andre
This covers mouse in,out,cancel. Axis (joystick) is still todo.
2016-05-31efl: Simplify pointer event names + add missingJean-Philippe Andre
No more difference between touch & mouse. Add axis, cancel, in and out.
2016-05-31ecore_evas: Pass mouse down,up,move with eoJean-Philippe Andre
This way, ecore sends eo events to evas, which can then be listened to by other clients (FIXME: the events will need to be propagated from evas to the elm window). Current support: - mouse/multi down - mouse/multi up - mouse/multi move - mouse wheel
2016-05-31evas: Move event feed and input to legacyJean-Philippe Andre
2016-05-31ecore_evas: Feed evas events with eo (down, up)Jean-Philippe Andre
2016-05-31ecore_input: Pass all events through direct cb firstJean-Philippe Andre
Since the direct input event callback returns true if the event has been processed, we can easily support legacy and progressively implement full support for eo input events.
2016-05-31ecore_evas: Register direct input cb from modulesJean-Philippe Andre
If the ecore_evas modules were using ecore_event_window_register() then they can also redirect everything though the direct callback instead.
2016-05-31ecore_evas: Add private direct callback for ecoreJean-Philippe Andre
All ecore_input_evas events should be passed through ecore_evas in order to avoid any information loss between ecore and evas. This is a private API.
2016-05-31Evas: Extend pointer events and add legacy conversion routinesJean-Philippe Andre
To be honest, this commit is a bit of a mess since it's a rebased version of some temporary work patches.
2016-05-31Evas: Fix compilation warnings (enum implicit cast)Jean-Philippe Andre
Moving enums to Efl renames them but keeps the value the same.
2016-05-31Evas.Canvas: Move some event_feed to legacyJean-Philippe Andre
Paving the way to Efl.Pointer.Event...
2016-05-31Efl: Add storage class Efl.Pointer.EventJean-Philippe Andre
This object is the data carried over in an event data pointer. The private data should be accessible by Ecore and Evas, but not externally. This means we should be able to easily extend the feature set, adding more and more information, without breaking API / ABI. Also, this should allow applications to create fake input events easily without exposing our internal structures, or functions with more and more parameters (such as feed multi). This is only a storage class, shouldn't contain any logic. In the future, some logic may be added for gestures support for instance, or input smoothing / resampling (eg. if input frequency is 90Hz and screen refresh rate is 60Hz). The aim is to replace: - Evas_Event_Mouse_Xxx - Evas_Event_Multi_Xxx - Ecore_Event_Mouse_Xxx We might want to also support Axis, Gestures, etc... with the same model or even same storage class.
2016-05-31Evas: EO-ify Evas_Device and partly move to EflJean-Philippe Andre
So, this is not a very clean solution, but this mostly makes Evas_Device an Eo object of class Efl.Input.Device. Since evas_device relies on some Evas knowledge (evas callbacks, canvas private data), it can't be fully moved to lib/efl/. Making the input device an interface rather than a class was also not a great solution, as the goal is to share the data structure around EFL internals (Ecore and Evas).
2016-05-31ethumb - don't complain to stderr about things that are handled by apiCarsten Haitzler (Rasterman)
things like load failures are up to api to deal with, not logs.
2016-05-31efl test suite - test args event and args valuesCarsten Haitzler (Rasterman)
2016-05-30elementary: Add a preview for icon themeAndy Williams
Not yet solved how to load an elm theme preview...
2016-05-30eina: Add non-allocated version to benchmarkFelipe Magno de Almeida
2016-05-30eina: Add mempool usage in benchmarkFelipe Magno de Almeida
2016-05-30eio: Fix eio_test_job_xattr testFelipe Magno de Almeida
Test wasn't enabled when modifications to function prototypes to eio_job_file_xattr_list and eio_job_file_xattr properties were made, so it got pushed inadvertidly without the necessary changes to user code.
2016-05-30elm_image: add a new eo property 'align' and implement related functionsJaeun Choi
previously, elm_image refered to align values set by evas_object_size_hint_align_set function to position the internal image inside an image object. size hint value is for positioning the image object inside its container object, so the previous code is inappropriate. this commit adds 'align' property for positioning the internal image.
2016-05-30elm init - add args event with ne efl loop argsCarsten Haitzler (Rasterman)
2016-05-30efl loop - add an args event and ability to produce itCarsten Haitzler (Rasterman)
this is an args event. right now we don't use it, but this should be done by some of the setup/init of an app and then produce an args event. the idea would be that this can be used by single-instance apps like web browsers, terminology to treat launch as an event.
2016-05-30Added feature to bring focused item to viewport on clickgodly.talias
Summary: Currently when an item in gengrid is focused and if it is scrolled off the viewport halfly and if it user clicks on it, it won't be scrolled into viewport. Only non-focused items will be scrolled into viewport when clicked. Test Plan: elementary_test -> Gengrid focus -> Click an item -> Scroll it little bit out of viewport -> Click again Reviewers: prince.dubey, shilpasingh, cedric, raster, SanghyeonLee Subscribers: seoz, rajeshps, govi, jpeg Differential Revision:
2016-05-30eet_image.c : Fix build warningJunsuChoi
Summary: initialized two variable for uninitialized build warning Test Plan: N/A Reviewers: woohyun, raster Reviewed By: raster Subscribers: cedric, jpeg Differential Revision:
2016-05-30elc_naviframe: Hide preserved content after its item is popped.Jaehyun Cho
Previously, preserved content was shown unexpectedly after its naviframe item was popped because the preserved content was not removed but was unset from its naviframe item. Since popped naviframe item becomes hidden on the screen, the preserved content of the popped naviframe item should become hidden by default as well.
2016-05-30elm: Fix efl_part inheritanceJean-Philippe Andre
So, I was storing a single "sd" pointer (class private data) but using it in two different places, ie. as if it were two different classes. Crashes happened, complaints were heard. See T3714.
2016-05-30Elementary: fix the indentationJaehwan Kim
2016-05-30elm_hover: Fix crash with efl_partJean-Philippe Andre
This fixes T3714 Efl.Part uses a basic inheritance for layout objects, but somehow this completely falls apart when the child class overrides all the functions. Weird. I'll check that more.
2016-05-30widget: set the parent-child relation again, when the widget is unsetJaehwan Kim
Summary: When the widget is unset from any container, a parent of the widget doesn't exist. So we should set its parent to the top object. But if we just set sd->parent, the parent can not find the widget as a child. So the container widgets set the parent-child relation when sub object is unset. This commit is related to 0822ad2195d335d65208856e6e590ac47691d920. @fix Test Plan: Check this issue. The unset widget don't added any widget as child. So when it set scale, the widget can not reload the thmeme. Reviewers: raster, cedric, Hermet, reutskiy.v.v Reviewed By: Hermet, reutskiy.v.v Subscribers: cedric, jpeg Differential Revision: Conflicts: src/lib/elementary/elm_mapbuf.c
2016-05-28eina_btlog: handle objective-c class methodsJean Guyomarc'h
Class methods signatures start with a '+'.
2016-05-28ector: fix redefinition of type and bizarre typedefJean Guyomarc'h
Maybe there is a trick here I am not aware of, but redefining a type as itself seems a mistake to me. This raised a warning anyway. Now it's gone.