[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: saving plots
From: |
James R. Phillips |
Subject: |
Re: saving plots |
Date: |
Mon, 19 Jun 2006 16:24:10 -0700 (PDT) |
>
> On 19.06.2006, at 10:03, address@hidden wrote:
>
> >
> >> On 6/18/06, Hayden Rampadarath <address@hidden> wrote:
> >>> how do you save plots using octave??
> >>
> >> Use the 'print' command. Type 'help print' at the Octave prompt.
> >
> > Unfortunately, in some circumstances the print command fails; in
> > particular
> > when the multiplot features of gnuplot are in use.
> >
> > In this case (and in all cases actually), your approach is still
> > sound, it just
> > needs a little modification.
> >
> > Replace "set" with "__gnuplot_set__", and you should be good to
> > go. It used to
> > be "gset", and you can still use that, but it is deprecated and may
> > disappear
> > in future versions of octave. "__gnuplot_set__" should be around
> > until octave
> > has an integrated whiz-bang graphics system, and no longer requires
> > sending
> > gnuplot commands directly from the octave command line.
> >
> > Jim Phillips
>
--- Matthias Brennwald wrote:
> Jim, thanks for this. Lets assume I want to implement some 'clone'
> function of the print command that allows working with multiplot
> using __gnuplot_***__ commands. Then, before a '__gnuplot_set__ term
> ps' command, the function should find out the current terminal, so
> that after 'replotting' the plot to a file, the terminal type can be
> reset to what it was before. I played with __gnuplot_show__ , but
> couldn't make it work. Any ideas on how to get the current terminal
> type?
>
> Matthias
Try
__gnuplot_set__ term push
__gnuplot_set__ term pop
jrp