|
From: | Michael Godfrey |
Subject: | [Octave-bug-tracker] [bug #32980] for backend FLTK, real is used for axes. double should be used |
Date: | Tue, 05 Apr 2011 18:30:16 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20100101 Firefox/4.0 |
Follow-up Comment #4, bug #32980 (project octave): It appears that a place where the axes can be checked for validity is after line 47 in axes.m. Two questions for anyone (John?) who knows this code: 1. Is this the right place? 2. Is it OK to put code which is conditional on the current backend at this point? I notice that currently the command: axis([0 Inf 0 200]) is processed without complaint, but it obviously does not work and trying to recover by axis([0 200 0 200]) which is what the axes were before does not bring back the plot correctly. So, it seems a good idea to provide an axes validity check in any case. Currently the checks for gnuplot (essentially valid range -max(double) to max(double)) and fltk/OpenGL are different, but both are needed. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?32980> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |