Emmanuel E wrote:
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
Yes. The event has an application defined number, and carries an id as
one of its parameters (wparam) that can be used by the receiving
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
3) The trapped events/messages are passed onto the thread waiting on that
queue
All the above is packaged and the user sees
The problem is how to do send messages back to the parent thread if it is
Dialog - it has to be woken up by a message from the windows queue -
which
is what happens in 3 above.
Do you mean to say you pass something other than window/screen updates as
messages? Cos in my experience if the
Do you mean to say you pass something other than window/screen updates as
messages? Cos in my experience if the parent thread is in Dialog() it
dosent
need to be woken up for updates to the screen.
We may be getting wires cross slightly - my poor explanation no doubt:)
When a thread is
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Plum, Jason
Sent: Monday, February 06, 2006 1:18 PM
To: perl-win32-gui-users@lists.sourceforge.net
Subject: RE: [perl-win32-gui-users] Multi-Threaded Example
This is actually rather simple.
Simple create a shared variable containing the a scalar handle
Please. Thanks!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Plum, Jason
Sent: Tuesday, February 07, 2006 2:24 PM
To: perl-win32-gui-users@lists.sourceforge.net
Subject: [SPAM] - RE: [perl-win32-gui-users] Multi-Threaded Example -
Email found
Hi all,
Apologies if I duplicate stuff that's already been said later in this
thread, but I've only go a few minutes to try and catch up.
I'll post a link to the code that Jez and I were working on at the end
of last year once I've got through the messages here.
Emmanuel E wrote:
But would
Jeremy White wrote:
A few months back I hinted at some code that Rob had built that would
make threading coding much easier for Win32-GUI apps. In light of your
recent examples, I've dropped him an offlist mail suggesting that his
code be available to more people. Although not complete, it
example in
addition to what yourself and Jez have worked on.
-Original Message-
From: Robert May [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 5:52 PM
To: Emmanuel E
Cc: Plum, Jason; perl-win32-gui-users@lists.sourceforge.net
Subject: Re: [win32gui] Re: [perl-win32-gui-users
Robert May wrote:
OK, my code is available from http://www.robmay.me.uk/win3gui/ - scroll
to the bottom and find the link for Win32::GUI::ThreadUtils
Typing too fast. That link should be:
http://www.robmay.me.uk/win32gui/
Rob.
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
-
From: Jeremy White [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 12:04 PM
To: Plum, Jason; perl-win32-gui-users@lists.sourceforge.net
Subject: RE: [perl-win32-gui-users] Multi-Threaded Example
Actually it was a mistake, thanks for sending it! I was starting to
wonder where the blazes
Hi Jason,
Cool stuff!
But would there be a way to avoid those select calls to spend some time
sleeping? I mean if there were a way to do a select on a thread queue it
would be great.
On the other hand why not call Win32::GUI::Dialog() in the main thread and
let the child threads update the
13 matches
Mail list logo
