Hi Everyone, I guess I've got a lot of catching up and reading to do!
Rob/Jeremy, I went through the ThreadUtils code and this is what I understood: 1) Youre using a Hook to trap events/messages sent to window controls 2) These are enqueued 2) The trapped events/messages are passed onto the thread waiting on that queue All the above is packaged and the user sees two methods: Call and AttachComms. Jason, I havent seen your latest code yet. Could you send it across? But what I was thinking is that if the parent thread is doing Dialog() anyway and if the worker thread IS getting passed the window or the control in some form or the other it really dosent change things much. The biggest advancement would be CLONE_SKIP, which allows you to create threads later. What I thought might be really useful is if one could use the select function call to wade through waiting sockets, thread queues or window events. Cheers, Emmanuel > --- Ursprüngliche Nachricht --- > Von: Robert May <[EMAIL PROTECTED]> > An: "Plum, Jason" <[EMAIL PROTECTED]> > Kopie: perl-win32-gui-users@lists.sourceforge.net > Betreff: Re: [win32gui] Re: [perl-win32-gui-users] Multi-Threaded Example > Datum: Tue, 07 Feb 2006 23:23:23 +0000 > > Plum, Jason wrote: > > WaitMessage... Ah, I was wondering what that was for.... The question I > > of course must supply is ... (dun dun dun) ... to attach said thread's > > queue to said function? > > Each windows gui thread has exactly one message queue. It is created by > the OS when the first win32 api call is made in that thread. The OS > then devlivers messages from other threads and from the window manager > that are destined for any window created by that thread to the thread's > message queue. > > The the application (Win32::GUI::Dialog() or one of it's alternatives to > be precise) takes over, pulling messages one at a time and dispatching > them to the actual window that they need to be delivered to. > > So WaitMessage() simply blocks the thread it is called from (and yields > processor resource to other threads/processes) while there are no > messages in the message queue of the calling thread. > > For more detail MSDN is the place to start - look up WaitMessage and > there are some links from the bottom of the page to more general windows > message processing descriptions. > > Rob. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Perl-Win32-GUI-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > http://perl-win32-gui.sourceforge.net/ > -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
