ecore-evas: set some properties even if engine function doesn't exist

elm uses these flags internally, so failing to set them even if the
windowing system doesn't support the operation can still cause apps to
behave differently

ref 723d4ca8c9
This commit is contained in:
Mike Blumenkrantz 2016-05-11 15:37:28 -04:00
parent 723d4ca8c9
commit 42e459b364
1 changed files with 4 additions and 0 deletions

View File

@ -1813,6 +1813,7 @@ ecore_evas_layer_set(Ecore_Evas *ee, int layer)
}
IFC(ee, fn_layer_set) (ee, layer);
IFE;
ee->prop.layer = layer;
}
EAPI int
@ -1874,6 +1875,7 @@ ecore_evas_iconified_set(Ecore_Evas *ee, Eina_Bool on)
}
IFC(ee, fn_iconified_set) (ee, on);
IFE;
ee->prop.iconified = !!on;
}
EAPI Eina_Bool
@ -1899,6 +1901,7 @@ ecore_evas_borderless_set(Ecore_Evas *ee, Eina_Bool on)
}
IFC(ee, fn_borderless_set) (ee, on);
IFE;
ee->prop.borderless = !!on;
}
EAPI Eina_Bool
@ -1924,6 +1927,7 @@ ecore_evas_override_set(Ecore_Evas *ee, Eina_Bool on)
}
IFC(ee, fn_override_set) (ee, on);
IFE;
ee->prop.override = !!on;
}
EAPI Eina_Bool