On 01/05/14 12:11, Yossi Kantor wrote: > Thanks for bringing to my attention that these are not callbacks but > inherited virtual functions. > So yes, my previous example is incorrect, those functions will be gone, > and replaced by normal Eo inheritance. > See, no need to get angry. Normal and constructive conversation will > solve everything.
I didn't get angry, I never got angry. I'm starting to get angry now though. Stop with the personal attacks and comments. If you'd like to be cocky and condescending at least don't be completely and utterly wrong, otherwise it just looks stupid, and is very annoying. The reason why I didn't further explain anything before is because your email: > Oh... that. > Nothing to worry about. The functionality of elm_widget_item STAYS AS > IT > IS. Just the names are gone. > Instead of doing *elm_widget_item_text_set_hook_set(stuf...) *it will > be > *eo_do(elm_object_item_text_hook_set, stuff...)* > (or even elm_object.. legacy if method is not protected)." Implied that you completely understood everything and have made a concious decision to ignore it, not that you are unsure, or have any doubts. To that I replied that not eliminating it is stupid, and then you went personal again. -- Tom. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
