interface Efl.Gfx.Image_Load_Controller ├ (P) load_size ├ (P) load_dpi ├ (P) load_region_support ├ (P) load_region ├ (P) load_orientation ├ (P) load_scale_down ├ (P) load_skip_header ├ (M) load_async_start ├ (M) load_async_cancel
Description
Description
Details
Details
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | None | T7873 efl.ui.image | ||
Resolved | None | T7880 efl.ui.bg | ||
Resolved | None | T7876 efl.gfx.image_load_controller |
Comment Actions
API looks strange, because it has load_async methods but no regular load. I understand that comes from Efl.File, but still, feels this feels like "everything we could not stuff into generic File or Image interfaces".
Besides this general comment, I see nothing obviously wrong.
I just updated the docs a bit.
Comment Actions
I'm removing the events from this since they duplicate the functionality of efl.gfx.image's events and there's probably no case when one would be used without the other.