backend switching broken

John W. Eaton jwe at octave.org
Thu Jul 23 16:43:01 CDT 2009


On 23-Jul-2009, Elias Pipping wrote:

| On Thu, 23 Jul 2009 14:35:43 -0400
| "John W. Eaton" <jwe at octave.org> wrote:
| 
| > On 14-Jun-2009, Elias Pipping wrote:
| > 
| > | --------
| > | Bug report for Octave 3.2.0 configured for x86_64-pc-linux-gnu
| > | 
| > | Description:
| > | -----------
| > | 
| > |   * Starting octave, running `backend("fltk")` and invoking plot
| > |     yields a plot in fltk. Switching to gnuplot using
| > |     `backend("gnuplot")` works, too -- the next plot will be done by
| > |     gnuplot -- but switching back does not, i.e. `backend("fltk")`
| > has |     no effect once gnuplot has been used. 
| > 
| > If I start a new Octave session and execute the commands
| > 
| >   backend ("fltk")
| >   sombrero
| >   backend ("gnuplot")
| >   peaks
| > 
| > both surfaces are drawn in the figure 1 window using the fltk
| > backend.  If I then do
| > 
| >   figure
| > 
| > the second figure window uses gnuplot.
| 
| That's not the problem I described. The problem I was seeing is being
| unable to switch back to fltk once i've switched to gnuplot and drawn
| something with it. No matter if I close all the figures or not.

The following works for me with the current sources and with 3.2.2:

  sombrero            # sombrero in gnuplot window
  backend ("fltk")    # backend for next new figure is fltk
  figure              # new fltk window opens
  sombrero            # sombrero in fltk window
  figure (1)          # switch back to gnuplot window
  peaks               # peaks in gnuplot window
  close all           # all windows closed
  peaks               # peaks in new fltk window
  close all           # all windows closed
  backend ("gnuplot") # backend for next new figure is gnuplot
  peaks               # peaks in gnuplot window
  backend ("fltk")    # backend for next new figure is fltk
  close all           # all windows closed
  sombrero            # sombrero in fltk window

If there is some other problem you are seeing, can you give a precise
list of commands that demonstrates the problem?

jwe


More information about the Bug-octave mailing list