comp.lang.idl-pvwave archive: archive » testing IDL

Home » Public Forums » archive » testing IDL_IDLBridge status

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: testing IDL_IDLBridge status [message #92246 is a reply to message #92245]

Thu, 05 November 2015 05:54

Jim Pendleton
Messages: 165
Registered: November 2011

Senior Member

On Thursday, November 5, 2015 at 6:32:24 AM UTC-7, superchromix wrote:
> After further investigation, it seems that there is really no way to do this. When the application object is busy, even though the status of the bridge object remains 0 or 2 (Idle or Command completed), the bridge object will not respond to the Execute method. I need to use Execute in order to query the status of the application.
>
> For example: (pseudocode)
>
> --------------------------------
>
> my_bridge = obj_new('IDL_IDLBridge')
>
> cmd = 'my_app = obj_new(''my_application'')'
> my_bridge -> Execute, cmd
>
> test_quit = 0
>
> while test_quit eq 0 do begin
>
> cmd = 'test_app_closed = ~obj_valid(my_app)'
> my_bridge -> Execute, cmd
>
> test_app_closed = my_bridge -> GetVar('test_app_closed')
>
> if test_app_closed eq 1 then begin
>
> obj_destroy, my_bridge
> test_quite = 1
>
> endif
>
> endwhile
>
> -------------------------------
>
> This doesn't work, because when the application is busy, the program gets stuck at the Execute statement. If this program is running in the main IDL process and gets stuck, then I can't do anything else in IDL while I'm waiting for the application to finish its task.
>
> If I use the NOWAIT keyword to Execute, and specify a callback procedure etc., it makes no difference. The program still gets stuck at the Execute statement.
>
> The "STATUS" property of the bridge is constantly reporting either 0 or 2 (IDLE or COMMAND COMPLETE) throughout this process. Even though the application is busy and is effectively blocking the bridge from doing any other processing, the status reports 0 or 2. Effectively, it is impossible for my program to query the bridge without getting hung up!
>
> Therefore, it seems there is no way for my to automatically kill the IDL bridge processes when the application objects are closed. Unless, there is a way for the application object to kill the IDL bridge process on its own, from within IDL?
>
> ideas?
> thanks
> Mark

Which platform and version of IDL are you using?

Report message to a moderator

[Message index]

		testing IDL_IDLBridge status By: markb77 on Thu, 05 November 2015 02:49
		Re: testing IDL_IDLBridge status By: markb77 on Thu, 05 November 2015 05:32
		Re: testing IDL_IDLBridge status By: Jim Pendleton on Thu, 05 November 2015 05:54
		Re: testing IDL_IDLBridge status By: markb77 on Thu, 05 November 2015 06:21
		Re: testing IDL_IDLBridge status By: markb77 on Thu, 05 November 2015 07:08
		Re: testing IDL_IDLBridge status By: markb77 on Thu, 05 November 2015 07:16
		Re: testing IDL_IDLBridge status By: Dominic[2] on Thu, 05 November 2015 09:00
		Re: testing IDL_IDLBridge status By: markb77 on Fri, 06 November 2015 00:50
		Re: testing IDL_IDLBridge status By: Jim Pendleton on Thu, 05 November 2015 18:02
		Re: testing IDL_IDLBridge status By: markb77 on Fri, 06 November 2015 01:19
		Re: testing IDL_IDLBridge status By: markb77 on Fri, 06 November 2015 06:10

Previous Topic:	Dates conversions
Next Topic:	memory leak in volume()

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 11:45:40 PDT 2025

Total time taken to generate the page: 0.00397 seconds