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

[John W. Eaton]

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

"So, yeah, one approach is to fill in the whole data model and let the GUI
framework deal with things"

I think you misunderstand what I mean by getting the full value back and what
is done with that in the model.

A copy of the octave_value object is returned, but the model/view actually
works with a QVector of objects for each cell in the display.  Those should
only be filled in with values as needed.  Not all at once on each update.  If
that is happening, I think it's an error.

Further, we can limit this to tabs that are actually visible, but then we need
another action so that we update when tabs become visible.

It's certainly possible to edit something while Octave is busy.  But the
action of that edit will be queued until Octave is otherwise idle.


    _______________________________________________________

Reply to this item at:

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

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