in reply to ReShow images without user interact with the GUI.

perlthrtut
Thinking of mixing fork() and threads? Please lie down and wait until the feeling passes-- but in case you really want to know, the semantics is that fork() duplicates all the threads. (In UNIX, at least, other platforms will do something different.) Similarly, mixing signals and threads should not be attempted. Implementations are platform-dependent, and even the POSIX semantics may not be what you expect (and Perl doesn't even give you the full POSIX API).
  • Comment on Re: ReShow images without user interact with the GUI.

Replies are listed 'Best First'.
Re^2: ReShow images without user interact with the GUI.
by Ace128 (Hermit) on Feb 04, 2006 at 10:59 UTC
    Hmm, ok, back to just threads then...

    Removing everything that got to do with forking from _thread_for_images and adding:
    threads->create( \&mainloop2() )->join;
    didnt help much since I get:
    thread failed to start: Usage: threads::new(classname, function_to_call, ...) at ...
    at the SECOND time it tries to create the thread! Which means, it works once! (so why not complaining then?)