Re: IDL and X and PS [message #593] |
Wed, 16 September 1992 07:38  |
knight
Messages: 37 Registered: January 1992
|
Member |
|
|
In article <15SEP199217204994@stars.gsfc.nasa.gov>, thompson@stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040) writes:
|> ... These system
|> variables will be different for the two different devices, and IDL does not
|> keep track of them as a function of device. Therefore, when the PLOT command
|> is executed on the PostScript file, the coordinate information for the
|> X-windows display is lost. The same thing happens when switching between
|> windows, or between plots generated with !P.MULTI.
|>
|> However, the following routine called SETPLOT can be used to replace SET_PLOT
|> to overcome this difficulty. I use this myself, and it fits my needs. It may
|> work okay for you to. It simply stores some of the most used system variables
|> in a common block as a function of plotting device and window.
|>
Thanks to Bill for sharing the setplot routine.
Another way to store the system variables is to write them to a save file:
save,/sys
and then recall them later:
restore
In this manner, you can recall the state from another device. This method is
an alternative to the one used in Bill's setplot. It avoids having to know all
the names of the system variables. You can restore system variables for your
favorite devices from files using the filename keyword. It is slower, and
avoids a common block (not a big deal). I'd call it an alternative to Bill's
method.
Fred
--
=Fred Knight (knight@ll.mit.edu) (617) 981-2027
C-483\\MIT Lincoln Laboratory\\244 Wood Street\\Lexington, MA 02173
|
|
|