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

Home » Public Forums » archive » Re: VM output under Windows
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: VM output under Windows [message #40814] Thu, 02 September 2004 18:07 Go to next message
biophys is currently offline  biophys
Messages: 68
Registered: July 2004
Member
It seems that Windows doesn't know how to display the output. Anyway,
I found Rick Towler's console object a very enlightening solution. I
just have to make some small changes to meet my needs. Basically I
just added a context menu so that it can save/clear what's in the text
widget. So now it can be easily used as a log console. Imagine how
wonderful to have your old console based programs running anywhere
interactively without adding complicated GUIs. :)
Re: VM output under Windows [message #40815 is a reply to message #40814] Thu, 02 September 2004 17:46 Go to previous messageGo to next message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
R.G. Stockwell writes:

> TEXT Widget!! I mean text widget, not test widget.

Oh, well, sure, a TEXT widget. But a *TEST* widget.
That would really have been something! :-)

Cheers,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Re: VM output under Windows [message #40816 is a reply to message #40815] Thu, 02 September 2004 14:35 Go to previous messageGo to next message
R.G. Stockwell is currently offline  R.G. Stockwell
Messages: 363
Registered: July 1999
Senior Member
"R.G. Stockwell" <noemail@please.com> wrote in message news:cnuZc.82$LC3.57229@news.uswest.net...
> I'd suggest making a test widget (for instance)
> and sending the output there.


TEXT Widget!! I mean text widget, not test widget.
Re: VM output under Windows [message #40845 is a reply to message #40816] Wed, 01 September 2004 18:05 Go to previous messageGo to next message
R.G. Stockwell is currently offline  R.G. Stockwell
Messages: 363
Registered: July 1999
Senior Member
"biophysics" <biophys@gmail.com> wrote in message news:512b0d8b.0409011529.2d8fffda@posting.google.com...
> Hi, guys
>
> If I simply use "print, var" in my code, I won't see any output from
> the virtual machine under windows. But it works fine if I start VM in
> a linux/unix terminal. Any idea of what's going on? Thanks!
>
> BTW: I start VM under windows by running "idlrt.exe vm="

WOW! I have never considered running a VM that was not
a GUI. Creative idea. :)

As to what's going on, the stdout for windows is perhaps not defined,
not opened or not realized etc. I'd suggest making a test widget (for instance)
and sending the output there.

-bob
Re: VM output under Windows [message #41658 is a reply to message #40814] Fri, 12 November 2004 00:46 Go to previous message
Georg Wiora is currently offline  Georg Wiora
Messages: 13
Registered: November 2001
Junior Member
biophysics <biophys@gmail.com> wrote:

> It seems that Windows doesn't know how to display the output. Anyway,

FSTAT says that the output unit -1 (stdout) is open, but obviously the
output is redirected to nowhere (or maybe to somewhere).

> I found Rick Towler's console object a very enlightening solution. I
> just have to make some small changes to meet my needs. Basically I
> just added a context menu so that it can save/clear what's in the text
> widget. So now it can be easily used as a log console. Imagine how

That sounds very good! Is your adapted version somewhere availible?
I did not even find the version of Rick Towler you mentioned. Any hints?

Georg

--
You may gratefully keep any typos you found in this message
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: UTM mapping problems
Next Topic: meshes and some irritations

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

Current Time: Wed Oct 08 16:12:47 PDT 2025

Total time taken to generate the page: 0.00492 seconds