Fixed and committed. First I've heard of these evas environment variables or that EWL generated warnings with them.
On 11/19/07, Brett Nash <[EMAIL PROTECTED]> wrote: > On Mon, 2007-11-19 at 19:54 -0500, dan sinclair wrote: > > I'm not seeing this when I have full debug on with Ewl. Can you please > > post an example program that shows this behavour? We've been trying to > > cleanup as many of the warnings as we can in the system. There are a > > few warnings spit but not many. > > That I find surprising. Obviously your set up is distinctly different > to mine. > > The easiest example I have is exhibit. I updated using easy_e17.sh on > the 14th of this month: > > % export EVAS_DEBUG_SHOW=1 > % export LD_LIBRARY_PATH=/opt/e17/libs/ > % exhibit |& grep 'EVAS ERROR' | wc -l > 814 > % > > That's opening my home directory. > > Jumping to a different machine (same update date), I get: > % ./ewl_embed_test |& grep 'EVAS ERROR' | wc -l > 60 > > Starting ewl_test and exiting gives: > % ./ewl_test |& grep 'EVAS ERROR' | wc -l > 105 > > I have another program which uses ewl (galaxie from thousandparsec) which > embeds > EWL widgets, which generates ~160 warnings when creating two ewl_tree, four > icons, > some labels, and a some various boxes and layout widgets. However the > others should be easier to test ;-) > > No special setup on either, using whatever the defaults are as installed > on both applications. > > Regards, > nash > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
