| Re: Speeding up data crunching using IDL_IDLBridge with asychronous execution [message #85195 is a reply to message #85194] |
Thu, 11 July 2013 16:20  |
natha
Messages: 482
Registered: October 2007
|
Senior Member |
|
|
On Thursday, July 11, 2013 4:50:45 PM UTC-4, Chip Helms wrote:
> So I suppose ideally, we should add this to the callback routine, right? Is there any way to identify which timer is associated with a given 'execute, /nowait' call?
It seems that the timer ID is concatenated to the other ones. So you just have to get the last ID. It works....
obridge=obj_new('idl_idlbridge')
for i=0,999 do begin
obridge->execute,'a=1',/nowait
while obridge->status() ne 0 do wait,0.0001
timer_id=widget_info(/managed)
ww=where(widget_info(timer_id,/event_pro) eq 'IDL_IDLBRIDGETIMER_EVENT',nn_w)
timer_id=timer_id[ww[nn_w-1]]
widget_control, timer_id, /destroy
print, memory(/high)
endfor
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
