jpeg pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=99d21f6d9c6e65e744f5276c9c01207385b75388
commit 99d21f6d9c6e65e744f5276c9c01207385b75388 Author: Jean-Philippe Andre <[email protected]> Date: Wed Mar 8 16:54:45 2017 +0900 evas: Print CRI message in case of bad event usage This will abort E when using Bryce and EINA_LOG_ABORT is enabled (it is enabled by default when running a non-release version of E). That's on purpose, as that code needs fixing :) Ref T3144 --- src/lib/evas/canvas/evas_events.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/evas/canvas/evas_events.c b/src/lib/evas/canvas/evas_events.c index a53bb12..82c6dd7 100644 --- a/src/lib/evas/canvas/evas_events.c +++ b/src/lib/evas/canvas/evas_events.c @@ -34,7 +34,7 @@ static inline void _evas_event_feed_check(Evas_Public_Data *e) { if (EINA_LIKELY(!e->running_post_events)) return; - DBG("Feeding new input events from a post-event callback is risky!"); + CRI("Feeding new input events from a post-event callback is risky!"); } #define EVAS_EVENT_FEED_SAFETY_CHECK(evas) _evas_event_feed_check(evas) --
