On 06/07/11 22:29, michael bouchaud wrote:
> I would like to clarify that I am very happy with the access
> elm_object_part_text_set. I do not question the API the problem is
> internal. I thinking about if things would be easier and more efficient,
> if we could provide a 'main edje' in elm_widget
On Wed, 6 Jul 2011 21:29:17 +0200 michael bouchaud
said:
elm_object_text_part_set(obj, "action", "text to set action to");
the widget would handle the action string case and set the appropriate
object/text inside the widget to the string provided.
> I would like to clarify that I am very happy
I would like to clarify that I am very happy with the access
elm_object_part_text_set. I do not question the API the problem is internal.
I thinking about if things would be easier and more efficient, if we could
provide a 'main edje' in elm_widget. And sure keep hooks
2011/7/6 michael bouchaud
2011/7/6 Tom Hacohen
> On 06/07/11 17:35, michael bouchaud wrote:
> > Hi, some of you seems really happy with the new elm_object_text_set
> > function, but it's not my case. I'm feeling very frustrated with it. The
> > implementation of this function is generic only because each widget knows
> >
On 06/07/11 17:35, michael bouchaud wrote:
> Hi, some of you seems really happy with the new elm_object_text_set
> function, but it's not my case. I'm feeling very frustrated with it. The
> implementation of this function is generic only because each widget knows
> where is the edje_object and the
Hi, some of you seems really happy with the new elm_object_text_set
function, but it's not my case. I'm feeling very frustrated with it. The
implementation of this function is generic only because each widget knows
where is the edje_object and the name of the part to set. Today each widget
who use
