[Octave-bug-tracker] [bug #53005] Variable editor: slow performance with large arrays

[John W. Eaton]

Follow-up Comment #28, bug #53005 (project octave):

OK, viewing the workspace of a function while debugging and also examining
them in the variable editor does seem to work for me.  I'm not sure what the
problem was before.

I saw the pr-output problem.  I think it is fixed now.

Yes, the autofit options no longer do anything.  They should be removed from
the dialog.  I just didn't know how to do that quickly.

The current auto-format selection only happens when the tab is first opened. 
I made that choice because it seemed wasteful to compute the formula on every
update.  But this choice is bad when values change, because the format can be
wrong.  Or it can be wrong for the values that are visible, because it is
based on the full array, not just the visible part.  But if we limit the
format selection to the visible portion it would probably be OK to update it
each time the refresh happens.  I will try to take a look at that.

I'm not sure what's happening with the bad format choice for zeros(50).  The
display in the terminal window is not bad, and the format selection should be
the same.  So maybe there is a minimum width being imposed for the variable
editor?  I'll check.

Could we close this report now and continue our discussion on other reports
about specific issues?

    _______________________________________________________

Reply to this item at:

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

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