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

[Dan Sebald]

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

Limiting the size is fine, but I think the better alternative is to make the
feature user-driven, not automatic auto-fit.  I can see how what I'm saying
about "auto auto" is somewhat obscure.  Imagine there is a button in the
header of the V.E.  The user presses the button and Autofit does its job.  (Or
if a button isn't preferred, make the action a right-mouse-click which creates
a local drop down menu of which "autofit" can be selected.)

The Autofit feature shouldn't run again and again with each processing
command.  I find that kind of annoying if I first manually slide the column
widths to what I like, run a command and then Octave shrinks all those column
widths again.  If I have my table view as desired, run a command, then the
table is showing a different collection of columns because of the resize I
have to go searching for the columns that were in view previously.

But I can see the usefulness of what I described in the first paragraph, i.e.,
that as a user I look at the V.E. table and decide it doesn't look correct so
I manually initiate an Autofit.  If I happen to have 1000x1000 array and that
takes 8 seconds, fine.  It's just once and until I press the Autofit button
again, there is no apparent lag in processing even though the V.E. is updating
the contents of the cells.

    _______________________________________________________

Reply to this item at:

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

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