comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Q: call_external hangs IDL Windows GUI?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Q: call_external hangs IDL Windows GUI? [message #43757 is a reply to message #43613] Wed, 27 April 2005 09:09 Go to previous message
b_gom is currently offline  b_gom
Messages: 105
Registered: April 2003
Senior Member
Josh,

not knowing exactly what you want to do, I'd suggest making a DLM with
one function that spawns a thread for computation, and another function
that polls to see if the thread is complete (by checking a global
variable for example). In IDL you'd either stay in a loop until the
polling function succeeds, or you'd set up a timer widget to
periodically check the thread status.

Brad


Joshua Lynch wrote:
> b_gom@hotmail.com wrote:
>> Joshua,
>>
>> call_external does block in Windows (there is no multi-threading in
the
>> IDL interpreter) You can, however, call an external function that
>> starts a thread and then returns quickly to IDL. You will have to
sort
>> out the messaging between the threads on your own though.
>>
>
> Any suggestions on how to make IDL wait until the thread is
completed?
> Is there a way to block on a variable (preferably not to busy wait)
in
> IDL and have the C code modify it? Or should I just go RTFM? :-)
>
> Thanks again.
>
>
> --josh
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: DLM on 64 bit machine
Next Topic: Re: Newline in widget_text

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 10:30:09 PDT 2025

Total time taken to generate the page: 0.40313 seconds