[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #53005] Variable editor: slow performance with large arrays
Date: Thu, 1 Feb 2018 16:54:23 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #53005 (project octave):

                  Status:               Confirmed => Ready For Test         


Follow-up Comment #19:

I pushed four new changesets that I think improve the performance and
appearance considerably.  The performance should be OK now regardless of
variable size, and the appearance should be good for moderately sized arrays.


There's a lot of work left to do, but I'm generally happy with the structure
now.  The code in pr-output.{h,cc} could use some love.  I intend to try, and
to get data lined up neatly in columns where possible (currently I think
lining up numbers on the decimal point only works for double and double
complex data).

Some other random things that may not have been discussed but that I've

* The workspace view is no longer upated at the debug prompt.  Is there a bug
report about that?  If it were, then you could use the variable editor to
easily track changes to variables as you step through some code in the
debugger.  This would be a really great feature to have.

* It would be nice if more than one tab could be visible at once.    That way
you could easily watch multiple variables while debugging.  Super killer
feature!  Is that possible with the Qt tab widget?

* Columns are automatically scaled now (at least for double and double complex
values) when the tab is created.  I agree that resizing on every update is
bad.  But it would be nice to have a button to force resizing to happen.  It
can matter because if the data switches from 1.23456 to 1.2345e+22, something
usually ends up cut off.

* There are many possibilities for cool features like filling rectangles with
a value, deleting or inserting rows or columns (more than one at a time), or
inserting another matrix using a command, not just by pasting.  It would be
nice to have a generic interface for this so that people could easily add
their own actions that are commands defined in .m files.

Anything else?  I hope this works better for those of you who have been
testing things recently.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]