On 05/15/2010 11:40 AM, Gustavo Sverzut Barbieri wrote: > On Sat, May 15, 2010 at 4:32 AM, Christopher Michael > <[email protected]> wrote: >> Working on an app that uses pause() to sleep until another process is >> finished it's setup, but I ran into an ecore_x issue. >> >> The first process spawns the second one, then calls 'pause()' to wait >> for the second process to get setup. >> >> The problem is that in the second process, ecore_x_init is called ... >> and something in ecore_x_init is causing my "pause()" to return ... so >> something in ecore_x_init is sending a signal to terminate, or a signal >> that is triggering a signal-catch function somewhere. >> >> In a nutshell, ecore_x is causing my pause() to return too early :( >> Anyone with some thoughts/suggestions ?? > > use ecore main loop primitives, like timer, fd or events for signal watching. > Thanks, but watching the signal(s) isn't the problem...that's fairly simple and straight-forward there ;) ... The problem is that ecore_x_init (or X itself) is sending a signal that kills pause...but I've discussed this with raster, and basically the use of pause() is not really the way I want to handle this, so it's a fundamental design flaw in my theory :) but after some discussion, I'm on the correct path now :)
dh ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
