On 2010-04-29 00:30+0100 Andrew Ross wrote: > On Wed, Apr 28, 2010 at 12:56:59AM -0700, Alan Irwin wrote: >> On 2010-04-27 00:11+0100 Andrew Ross wrote: >> >>> The xwin problem [for the interactive octave examples] is simple - and >>> nothing to do with the p?? examples. Your >>> script called figure with a file name set. This doesn't make sense for >>> interactive drivers. >> >> Thanks for fixing this. As a result, -dev xwin is now our best interactive >> octave device so I have expanded the number of p examples accordingly >> (revision 10941). p11, p14, p19, and p20 still have some showstopper >> issues with -dev xwin so had to be dropped from the list until those issues >> are fixed. Also, p21 produces a blank black page which is also probably an >> error (although not a showstopper). > > Alan, > > I've fixed the issue with p11. > > p14 does not display properly for me (for reasons I don't understand). > The axes rather than the mesh are animated. It works fine if called > directly from octave in the bindings/octave directory so it is something > about the way the test script works.
Hmm. p14 works for me with Octave-3.0 (Version 1:3.0.1-6lenny3), Both the mesh and the axes are animated (presumably the latter because the scales are changing). > > I've changed example 12 so that you no longer have to press a button in > example 20 to get the last plot (was this your issue?) > > All other xwin examples are fine - I do not see your issues with 19 or 21. > Which version of octave are you using? I have tested with 3.2. All is reasonably well now for test_octave_xwin with 1:3.0.1-6lenny3. Some of these interactive examples are really cool. I particularly like the "p18" 3D perspective plot which you can interactively view from various orientations chosen by dragging the mouse. I worked that one really hard, and it eventually failed (black frozen plot). Which is why I said "reasonably" above. I doubt that bug is worth chasing directly, but perhaps we will get some more insight on the source of the unreliability as we get more device drivers to work as well as xwin does for these examples. > Well it looks like choosing tk as a driver just does not work at the > moment with octave and probably hasn't for a fair while. figure.m contained > code which called extensions in the tk driver for this particular case. > The current build system certainly does not generate octave bindings for > these, hence the failure. I've commented out these extensions and octave > now works with just the standard tk driver again. Results are comparable > to the xwin driver since tk support plGetCursor. I don't propose to do > anything more with the tk support since I don't fully understand it, I > don't use it, and clearly no-one else does with tk or they would have > filed a bug report a long time ago. That sounds the right way to go. I confirm that test_octave_tk works as well as test_octave_xwin. Thanks for these many improvements. There are obviously quite a few issues left as noted in plplot_test/test_octave_interactive.sh.in, but these interactive octave results are quite an improvement over what we had before. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
