summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJean-Philippe Andre <jp.andre@samsung.com>2017-03-08 16:54:45 +0900
committerJean-Philippe Andre <jp.andre@samsung.com>2017-03-08 17:04:57 +0900
commit99d21f6d9c6e65e744f5276c9c01207385b75388 (patch)
treedf984774aa284c3b7e66801818512b18d3404e9f
parentb9ab5f68aff23349a1c63079dbbed48d7cdf0c3d (diff)
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
-rw-r--r--src/lib/evas/canvas/evas_events.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/evas/canvas/evas_events.c b/src/lib/evas/canvas/evas_events.c
index a53bb12d85..82c6dd7c38 100644
--- a/src/lib/evas/canvas/evas_events.c
+++ b/src/lib/evas/canvas/evas_events.c
@@ -34,7 +34,7 @@ static inline void
34_evas_event_feed_check(Evas_Public_Data *e) 34_evas_event_feed_check(Evas_Public_Data *e)
35{ 35{
36 if (EINA_LIKELY(!e->running_post_events)) return; 36 if (EINA_LIKELY(!e->running_post_events)) return;
37 DBG("Feeding new input events from a post-event callback is risky!"); 37 CRI("Feeding new input events from a post-event callback is risky!");
38} 38}
39 39
40#define EVAS_EVENT_FEED_SAFETY_CHECK(evas) _evas_event_feed_check(evas) 40#define EVAS_EVENT_FEED_SAFETY_CHECK(evas) _evas_event_feed_check(evas)