2010/12/9 Brett Nash <n...@nash.id.au>: > On Thu, 2010-12-09 at 09:31 -0200, Iván Briano (Sachiel) wrote: >> 2010/12/9 Brett Nash <n...@nash.id.au>: >> > 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. >> > >> >> What about calling it with a font and size = 0? Does it make >> sense to have a 0 sized font, or should it keep the current one >> while setting the new font? Assuming it's not doing that already. > > Sorry if I wasn't clear. Currently passing in _either_ a NULL font or a > 0 size font just causes the function to fail. And you are correct that > a 0 point font is down right silly. > > So yes, a call to set the font, and NOT the size would also work. My > experience in past has been setting the font size is common, but > changing the font without changing the size is less common. But that > may be conceit to the way I program ;-) >
No clue, I don't really change fonts in code usually, but since we have enough ambiguous things around already I thought that, for a change, it would be nice to be all clear about it. > 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
