Dirk Meyer wrote:
> Lars Eggert wrote:
>> One thing I've seen mentioned is that forking from the main thread
>> will not results in children with blocked signals. If this is true
>> (and I haven't tested it), then we can work around the issue by using
>> the main thread as a fork proxy: Have all threads talk to the main
>> thread when they need to fork something, and have the main thread do
>> the fork and return child information.
>
> Cool that works. Any good ideas how to do that? Right now I just send
> an event ('fork', childapp, comand) and let the main thread start
> it. It looks like a bad hack but it's much better than using runapp.
One last thing: _if_ we do it that way, I need a function to get the
information if this is the main thread. It would be stupid to send an
event and wait for the main thread to fork when it is the main thread
(stupid as in it won't work).
Dischi
--
My mind not only wanders, sometimes it leaves completely.
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
