[Octave-bug-tracker] [bug #32980] for backend FLTK, real is used for axes. double should be used

[Rik]

Follow-up Comment #19, bug #32980 (project octave):

Mapping the data seems fine.  To get it to work I had to move the mapping of
{x,y,z}tick ahead of the for loop because the call to set (h, 'ydata', ydata)
updates the ylimits which are then wrong in the ymap function.

How were you thinking of implementing this?  I just reread the discussion and
JWE seemed reluctant to put this in axes.m.  You mentioned putting equivalent
code in __init_fltk__.cc?





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32980>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/