Nick Hughart schrieb: > On Fri, 08 May 2009 19:46:26 +0200 > Peter Wehrfritz <[email protected]> wrote: > > >> [email protected] schrieb: >> >>> Ok another question, >>> >>> what about the case whene we dont know the stat of the widget. So >>> we must get the stat first and then decide wether to call >>> ewl_widget_enable or disable. How can I do to obtain this stat? >>> >> if (DISABLED(w)) >> ewl_widget_enable(w); >> else >> ewl_widget_disable(w); >> > > Why is DISABLED a macro instead of a function like > ewl_widget_disabled()? Optimization reasons? >
Well, ewl_widget_disabled_is() could also be done by a macro. We actually have some of such function-like macros. There also some un-namespaced macros like DISABLE(), VISIBLE(), CURRENT_W(), REALIZED(), etc. I don't know why they don't have a namespace, they have been there long before me. Probably a relict of the early days, but Nathan can answer that probably better. On the long run they need to be renamed, but I always hesitated to do the work :). Peter ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
