comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Capturing stdoutput

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

Re: Capturing stdoutput [message #11818 is a reply to message #11636]

Fri, 22 May 1998 00:00

J.D. Smith
Messages: 214
Registered: August 1996

Senior Member

Bernard Puc wrote:
>
> Hello,
> I am looking for ideas on how to implement the following: I have a
> widget application and I want to display whatever output various
> procedures/functions usually write to the output log window in a text
> window in the application. Any hints are welcome.
>
> -Bernard Puc
> puc@gsfc.nasa.gov

This points to the need I see for IDL to contain a general *information* catching
mechanism. I.e., I mean that:

message,'This message',/INFORMATIONAL

would send a signal, not of an error, but of an info type, which could be caught
with catch.

Then, e.g., we simply could say:

catch,info,/INFORMATIONAL
if info ne 0 then widget_control,log,set_value=!INFO_STRING

and redirect all info into our widget. This way, a program run on the command line
would give info on the command line, but we could easily put that info anywhere else
if we so choose.

JD
--
J.D. Smith |*| WORK: (607) 255-5842
Cornell University Dept. of Astronomy |*| (607) 255-4083
206 Space Sciences Bldg. |*| FAX: (607) 255-5875
Ithaca, NY 14853 |*|

Report message to a moderator

[Message index]

		Capturing stdoutput By: Bernard Puc on Thu, 21 May 1998 00:00
		Re: Capturing stdoutput By: J.D. Smith on Fri, 22 May 1998 00:00
		Re: Capturing stdoutput By: Alex Schuster on Fri, 22 May 1998 00:00

Previous Topic:	Q: A good way to interrupt and kill procedures?
Next Topic:	Euclidean distance

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 05:29:29 PDT 2025

Total time taken to generate the page: 0.09865 seconds