I'm experiencing some odd behaviour with a win32::GUI app. I'm not sure if
this is the best place to post, but I figured it would be a good start.
I have an app that does scanning and document capture. The problem I'm
experiencing is that when I click the scan button, everything executes up t
I'll include the handler and the scan function below, as both are
relatively short. Note that in the DoSCAN function, the scan button
(called $scan) is disabled right before the system call. When I click the
button, it is immediately disabled. So I know it's getting to that point.
But then
Thanks for the idea! That seems to be more responsive, except that the
ShellExecute command doesn't block until Acquire exits. Is there a way to
make this block?
Scott
- Original Message -
From: "Jeremy White" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
Sent: Thursday, December 01
Thanks for the idea! That seems to be more responsive, except that the
ShellExecute command doesn't block until Acquire exits. Is there a way to
make this block?
There should be - there are lots of options which aren't documented, have a
google for ShellExecute for other environments, that s
I've not used it myself, but I'd take a look at Win32::Process (standard
with ActiveState Perl), which has a Wait() method to allow you to wait
for a process to finish.
As an aside: ShellExecute() always returns once the process it is
launching has started. ShellExecuteEx() can give you a hand
5 matches
Mail list logo