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
This commit is contained in:
parent
b9ab5f68af
commit
99d21f6d9c
|
@ -34,7 +34,7 @@ static inline void
|
||||||
_evas_event_feed_check(Evas_Public_Data *e)
|
_evas_event_feed_check(Evas_Public_Data *e)
|
||||||
{
|
{
|
||||||
if (EINA_LIKELY(!e->running_post_events)) return;
|
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)
|
#define EVAS_EVENT_FEED_SAFETY_CHECK(evas) _evas_event_feed_check(evas)
|
||||||
|
|
Loading…
Reference in New Issue