comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Re: IDLVM and retall

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

Re: IDLVM and retall [message #50039 is a reply to message #50027]

Tue, 05 September 2006 08:31

Foldy Lajos
Messages: 268
Registered: October 2001

Senior Member

On Mon, 4 Sep 2006, JD Smith wrote:

>
>
> I have a large widget program which runs (optionally) under the IDLVM.
> Around IDL version 6.0, when the VM was introduced, there was an
> inconsistency in how non-blocking widgets were dealt with in the VM
> vs. a normal IDL session, which was fixed in IDL 6.1:
>
> Beginning with IDL 6.1, the XMANAGER procedure honors the value of
> the NO_BLOCK keyword in Runtime and Virtual Machine modes.
>
> Because XMANAGER did not honor the NO_BLOCK keyword in previous
> releases, widget applications that worked properly (that is, not
> blocking) when run in a licensed full version of IDL behaved
> differently when run in Runtime or Virtual Machine mode. This
> difference in behavior has been removed; widget applications should
> behave identically (with regard to blocking behavior) in all IDL
> licensing modes.
>
> Other differences between IDL's Virtual Machine mode and full
> licensed mode, such as the fact that programs that call the IDL
> EXECUTE function will not run in the IDL Virtual Machine, are still
> in effect. If you have modified your widget application to work
> around the old blocking behavior by removing the NO_BLOCK keyword
> from calls to XMANAGER or by substituting the JUST_REG keyword, you
> may need to reinsert the NO_BLOCK keyword to achieve the desired
> behavior.
>
> My program has an error catching system that differentiates between
> two modes: running with a GUI, or running "lights-out" as a script.
> In the former case, the error is caught, displayed for the user with
> DIALOG_MESSAGE, and the RETALL command is then issued to return all
> the way back to the active command line, letting the program continue
> to run. When running as a script, instead MESSAGE is called, and the
> error halts the program.
>
> What I have just discovered, to my dismay, is that RETALL completely
> closes down an IDLVM session, rather than returning to its
> "non-blocking" widget event processing shell, as the above 6.1 update
> note would imply.
>
> Here's an example
>
> ;;; file test_vm.pro
> pro test_vm_event, ev
> a=dialog_message('Testing RETALL',/ERROR)
> retall
> return
> end
>
> pro test_vm
> b=widget_base(/ROW)
> but=widget_button(b,VALUE='Do It!')
> widget_control, b,/realize
> XManager,'test_vm',b,/NO_BLOCK
> return
> end
>
>
> Run TEST_VM in a fresh IDL session, and you'll see a button. Click
> it, get an error message 'Testing RETALL', but the tiny app will
> continue to run (the desired behavior).
>
> Now compile it to a .sav file:
>
> IDL> save,FILE='test_vm.sav',/ROUTINES
>
> quit IDL, and then:
>
> % idl -vm=test_vm.sav
>
> You'll see the same button. Click it, get the 'Testing RETALL'
> message, but notice that now when the message is dismissed and RETALL
> is called, the entire IDLVM session is shut down! I'm not sure why
> this is the case, but I need a way to work around it. Since there are
> many simultaneous event components all injecting events into the
> program suite, there is no convenient place to put a top level CATCH.
> I was relying on the background event processing inside of IDL to
> continue to run, i.e. to serve as an absolute top-level catch, but it
> doesn't do so in the VM.
>
> Suggestions appreciated.
>
> JD
>

probably a CATCH in main helps. It works in IDL 6.2 (linux).

regards,
lajos

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;
;;; file test_vm.pro
pro test_vm_event, ev
on_error, 1
a=dialog_message('Testing RETALL',/ERROR)
message, /noprint
return
end

pro test_vm
b=widget_base(/ROW)
but=widget_button(b,VALUE='Do It!')
widget_control, b,/realize
XManager,'test_vm',b,/NO_BLOCK
return
end

while 1 do
catch, status
if status ne 0 then catch, /cancel
wait, 1
endwhile

end

Report message to a moderator

[Message index]

		Re: IDLVM and retall By: JD Smith on Fri, 08 September 2006 09:35
		Re: IDLVM and retall By: JD Smith on Fri, 08 September 2006 09:30
		Re: IDLVM and retall By: JD Smith on Fri, 08 September 2006 09:26
		Re: IDLVM and retall By: JD Smith on Fri, 08 September 2006 09:12
		Re: IDLVM and retall By: news.qwest.net on Fri, 08 September 2006 09:10
		Re: IDLVM and retall By: btt on Fri, 08 September 2006 09:02
		Re: IDLVM and retall By: news.qwest.net on Fri, 08 September 2006 08:42
		Re: IDLVM and retall By: David Fanning on Fri, 08 September 2006 08:28
		Re: IDLVM and retall By: btt on Fri, 08 September 2006 07:57
		Re: IDLVM and retall By: David Fanning on Thu, 07 September 2006 21:00
		Re: IDLVM and retall By: JD Smith on Thu, 07 September 2006 15:57
		Re: IDLVM and retall By: David Fanning on Thu, 07 September 2006 12:14
		Re: IDLVM and retall By: JD Smith on Thu, 07 September 2006 11:54
		Re: IDLVM and retall By: David Fanning on Thu, 07 September 2006 06:52
		Re: IDLVM and retall By: JD Smith on Thu, 07 September 2006 01:57
		Re: IDLVM and retall By: JD Smith on Wed, 06 September 2006 23:21
		Re: IDLVM and retall By: Foldy Lajos on Wed, 06 September 2006 12:30
		Re: IDLVM and retall By: JD Smith on Wed, 06 September 2006 11:53
		Re: IDLVM and retall By: Foldy Lajos on Tue, 05 September 2006 08:31
		Re: IDLVM and retall By: David Fanning on Fri, 08 September 2006 09:48

Previous Topic:	Re: ascii_template advanced
Next Topic:	IDLVM and retall

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 19:37:28 PDT 2025

Total time taken to generate the page: 0.00429 seconds