Hello,
Quick proposal:
evas_object_text_font_set(Evas_Object *text, const char *font,
Evas_Font_Size size)'
Currently rejects a NULL font or non-positive size. So calling:
evas_object_text_font_set(label, NULL, 12);
is an (expensive) no-op.
I propose that calling it with a NULL font just changes the size, using
the current font.
FROs: (Frequently Raised Objections):
So who is going to write this magical and revolutionary code?
If people think it's a good idea, I'll do the patch _and_ update
the
currently non-existent documentation.
How does this affect current code?
Code currently calling it with NULL args and expecting nothing to
happen will break. This code should be taken out an shot. Well
behaved code will not be affected.
And this helps how?
Changing font size no longer needs to do a font_get followed by a
font_set.
Is there another way?
Sure; add a specific font_size_set call, but why add an extra call
when
an obvious extension to the existing API will do the job.
Could we do it for Evas 1.1 instead?
Yep, in which case I'll write the patch, and apply it later.
Is this an argument?
No, an argument is a connected series of statements intended to
establish a proposition.
Regards,
nash
------------------------------------------------------------------------------
This SF Dev2Dev email is sponsored by:
WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
