In case any of the calls to ActiveX don't return quickly, I
wanted to use a ProgressBar and Timer to provide visual feedback
that something is happening. But I found that the Flex Timer pauses
while calling ActiveX.
To illustrate, I've simplified the Flex program in the above
example and attached it below. If you run this code from within a
setTimeout function is initiated with a 5 second delay.
ticking, and you can see updates to the ProgressBar. But if the
setTimeout function is replaced by a
new ActiveXObject statement as in the sample from the above
link, and the instantiation of the ActiveX object takes some time,
the Flex Timer pauses during the ActiveX instantiation; i.e., the
ProgressBar does not update while the
new ActiveXObject call is taking place. In order to see
this, you can use the example from the link above and put a
Sleep call in the constructor of the ActiveX object.
Does anyone know why this happens, or if there's a way to
keep the Flex Timer running while the call to ActiveX is taking
I've read that there is a Flash Player script timeout of 15
I'm not sure if that timeout is related to ExternalInterface
calls, but I was able to Sleep for up to 2 minutes in the ActiveX
constructor, and the Flash Player patiently waited; it never threw
a ScriptTimeoutError. --Bruce