This is public API. even if you have used for only gengrid, the pulic API user
can use it for another widget. we have to ensure same result as before.
I can see you intention, but this hides a bug, the API is there to adjust what interest_region_get is returning. And when you set it to item, only gengrid will respect that. So all in all you now can set that, verify that it is really set, and get the coordinates, just to realize that you did not get the item but rather the widget.
No other widget than gengrid does implement this, so whenever you used that outside gengrid, then you are asking for trouble, you did something in your code which is not working ...
If there is another widget, then this should probebly also be added to this, but i pretty much don't see a single usecase where this helps ... Additionally, i would actaully prefer focus_region_show_mode not beeing part of the Efl_Ui_Widget private data. As this is not used there...
@YOhoho do you have a usecase where this definitly needs to return a wrong value ?
There is a unit test failure reported by tizen unit test.
Evas_Object *list = elm_list_add(p); elm_object_focus_region_show_mode_set(list, ELM_FOCUS_REGION_SHOW_ITEM); if (elm_object_focus_region_show_mode_get(list) != ELM_FOCUS_REGION_SHOW_ITEM) test fail
As you said, only gengrid implements that property. so i think it is invalid unit test. list widget was replaced with gengrid widget. never mind about this patch.
By the way, we can add documentation this API only work for gengrid.