On 04/07/11 11:12, Mike McCormack wrote: > How about this: > > elm_object_label_set -> elm_object_text_part_set > elm_object_label_get -> elm_object_text_part_get > > but keeping the elm_object_text_set/get macros as they are. i.e. > > EAPI void elm_object_text_part_set(Evas_Object *obj, const char *item, const > char *label); > #define elm_object_text_set(obj, label) elm_object_text_part_set((obj), NULL, > (label)) > > I like elm_object_text_set() for the default part as it's short and simple. > Using "label_set" for the name was to keep it separate from "text_set", but > I agree "text_part_set" is good.
Yeah, that's exactly what I meant. :) I'm glad you agree, will change it soon. -- Tom. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
