Usually, evas_object_resize() or evas_object_size_hint_min_set() cannot resize object, because they are called internally in sizing eval cycle and overwrite the value set by hand.
If someone wants to make an exact 200 * 100px Elm_Button, he should pack button with grid or layout (with customized edc). Also, table and rectangle packed into same cell with widget can be a solution. However, that is not intuitive way, especially to the first learner of EFL. They just wanted a button with proper size, but to make it is too hard, and there are many things to learn. I suggest elm_object_min_set/get() api. "size_hint_min" is determined to show widget properly. For example, button's min size is determined to show its icon & text fully. If app developer tries to reduce the size under "size_hint_min", it will break the layout, so it doesn't need to be applied. However, app developer wants to increase the size, it should be allowed, unless it breaks the calculation logic or hierarchy. (I don't think that changing button size as one likes is an unreasonable demand.) The next patch includes the change for my suggestion. Any comments are welcome. I do not insist my suggestion is an absolute one solution to this problem, but I want to raise it to solve together. Thank you. Regards, conr2d https://phab.enlightenment.org/D3270 ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
