do a thaw eval after thaw to ensure we dont miss any events
freeze stops events (in/out/down/up and so on, not del etc.) and thaw does the oppostie. the thing is thawing to 0 freeze level never re-evaluated everything. it was an optimization and simpler. so to re-evaluate state and not lose thngs like in and out evets you do have to do a thaw eval after thaw that will evaluate that state and produce in and out events if you thaw back to 0. i don't know if this fixes T4194 or not, but it does dot an i and cross a t.
This commit is contained in:
parent
6bf2116206
commit
0fcd99cda5
|
@ -5121,6 +5121,7 @@ _smart_size(Evas_Object *obj, int w, int h, Eina_Bool force)
|
|||
_smart_calculate(obj);
|
||||
_smart_apply(obj);
|
||||
evas_event_thaw(evas_object_evas_get(obj));
|
||||
evas_event_thaw_eval(evas_object_evas_get(obj));
|
||||
}
|
||||
|
||||
static Eina_Bool
|
||||
|
|
Loading…
Reference in New Issue