On 10/21/05, Michael Jennings <[EMAIL PROTECTED]> wrote:
On Tuesday, 18 October 2005, at 23:09:07 (-0500),
Nathan Ingersoll wrote:
> I have never liked the parameter inconsistency in the widget constructor
> calls, but have been content to support them as people are used to it from
> other toolkits, and it can save them some extra lines of code. As part of a
> general cleanup, dan and I decided that we valued API consistency over the
> minimal savings in lines of code. So constructors such as ewl_entry_new(char
> *text) become ewl_entry_new(), and followed by a call to
> ewl_entry_text_set(Ewl_Entry *entry, char *text) to set it's text.
You could always do both:
ewl_entry_new()
ewl_entry_new_with_text(text)
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]>
n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
"Remember kids, if there's a loaded gun in the room, be sure that
you're the one holding it." -- Captain Combat
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
