Jihad Battikha wrote:
>Hi,
>
>Please excuse me if this has already been asked numerous times on this
>list (I'm new to the list).
>
>I'm trying to implement a very simple Win32::GUI application which is
>able to listen on an open socket for incoming connection requests (this
>problem doesn't *really* have to do with sockets, though). My problem
>is that the script doesn't get to the socket code until the GUI is
>destroyed or I outright call it with a UI action (button click or
>something). The script does respond fine to UI actions but even when I
>create a button to instantiate the socket code as a subroutine (instead
>of being called at script execution), the socket code blocks and then I
>can't use the UI until I kill the socket portion. :-(
no luck, Jihad :-(
you'll need a full blown multithreaded perl to do what you want within
a single script... support for it is not yet mature, but it's in
developement. the only resort is a two-script solution; you may eventually
try with some Win32-specific interprocess communication mechanism
(Mutex, Semaphore, Event, Shared memory, ...) to ensure that you can
control your child script appropriately.
HTH.
cheers,
Aldo Calpini
<[EMAIL PROTECTED]>
