I have a question about the main loop in ewl (or ecore really).

I'm trying to create an Ewl-Sharp library and I'm having a problem
exitting the main loop function.

In fact once I call ewl_init(argc, argv); I can't exit the program without
calling ecore_shutdown(); and getting a "Power Failure" message, or
hitting Ctrl-C to kill the program. I don't even need to be going into
ewl_main(); for it to do this.

I think something may be going out of scope.
I know that the ewl_main_quit(); function doesn't kill it right away, but
says that "Quits the main loop once all the events currently on the queue
have been processed." but this doesn't seem to be the problem, I can get
out of the main loop fine, I've proven this by compiling printf statements
into the code for debugging. The program just sits there after the main
loop doing nothing, or what I perceive as nothing anyway.

So I guess my question is: Is there anything that ewl_init() or
ecore_init() set up that could cause the program to freeze if they went
out of scope, or could a pointer get lost if I'm not preserving something
on the managed code side?  Everything else is going so smooth as ewl is
completely serialized.  No C-Glue like the gtk libs need :)

Anyone have an Idea on this... and anyone who wants to help out is welcome
as well.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to