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

[Dan Sebald]

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

I just thought: the idea of dynamically adjusting the data content of the
displayed table may be a no-go in the sense that the V.E. sliders no longer
work in that scenario.

I'm trying out some things in the current V.E.  One thing I notice is that
auto-fit works in terms of column-width but not in terms of row height.  I
select "Uniform" auto-fit in the Preferences, select OK and when I look at the
Preferences again it is back to "By Column".

The main observation though is that when I turn off "Autofit" there is no lag
in refresh and the V.E. works great, e.g.,


>> x = rand(1000);
>> x(1:5,1:5) = x(1:5,1:5).^2;


As far as a solution, how about simply getting rid of Autofit feature or
perhaps redefining what it means to something else.  For example, autofit
might just apply to when someone edits the contents of a cell.  I'd say to try
an make the feature something inherent to frameworks table behavior, as
opposed to something that loops through each individual cell and update width
(if that is what's currently done).

As an example, the current behavior the following is a bit odd.  Turn on
Autofit (undock the V.E. to see what is happening) then type:


>> x = zeros(1000);
>> x(999,999) = 123456789;


As far as what's visible, why should every column be widened the same as 999?

Anyway, can one come up with a meaning for Autofit that is still useful but
not so global?

    _______________________________________________________

Reply to this item at:

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

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