On Mon, 06 Sep 2004 00:01:48 +0200 Kim Woelders <[EMAIL PROTECTED]> babbled:
It seems to me that it should be possible to shut down ecore-x and the X connection without closing the display. I believe this is necessary if one process using ecore-x forks off a child that calls ecore_x_init(). If there are no objections I will commit attached patch.
errr - shutting it down and closing the display connection are the same thing. once the display connection is closed (you go and close the actual fd in your patch) the connection is useless and you will get IO errors. i'm not sure what this gains you.
When E16 (in CVS branch-exp) forks off children to manage secondary screens it goes like this:
ecore_x_init(":0.0");
...
if (!fork()) {
ecore_x_disconnect();
ecore_x_init(":0.1");
}
...
ecore_x_shutdown();If the child calls ecore_x_shutdown() in stead of ecore_x_disconnect() the parents X-connection is killed (by XCloseDisplay). If the child just starts with ecore_x_init() it's like a nop because ecore_x_init() only does actual work on first invocation.
If this should be done some other way I'm all ears :)
/Kim
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
enlightenment-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
