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

Home » Public Forums » archive » Why Output Keywords Fail in cgWindow
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Why Output Keywords Fail in cgWindow [message #85472 is a reply to message #85468] Mon, 12 August 2013 05:25 Go to previous messageGo to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Fabien writes:

> I think it is more related to the use of _EXTRA keywords, isn't it?
>
> IDL> help, _EXTRA={MEMORY:1, OUTPUT:mem_out}
> % HELP: Expression must be named variable in this context: <STRING
> Array[1]>.
> % Execution halted at: $MAIN$

Yes, it is related to the use of the _EXTRA keyword. Without saving
every keyword explicitly, and then calling it explicitly, there is no
way to recover the keyword value from Call_Procedure.

I could, of course, do something like this for a handful of graphics
commands (say, the Coyote Graphics commands), by turning the graphics
commands into objects. But, I envisioned cgWindow as a program that
could work with *any* IDL graphics command, even those that I didn't
write.

Cheers,

David


--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Persistent environment variables (in DLM example)
Next Topic: IDL_IDLBridge: No gain?

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

Current Time: Wed Oct 22 18:03:04 PDT 2025

Total time taken to generate the page: 0.65063 seconds