[Top][All Lists]

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

[Octave-bug-tracker] [bug #53046] Variable Editor: feature request to ma

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #53046] Variable Editor: feature request to make multiple tables visible at once.
Date: Wed, 14 Feb 2018 00:44:57 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #8, bug #53046 (project octave):

Thanks.  That is definitely more flexible than tabs alone.

After playing with it for a few minutes, I noticed a few things:

I can see how to overlap two variable windows so that they behave like a
tabbed interface.  Having the tabs on the bottom is OK, but I think most
people would expect the tabs to be on top, and with buttons on the tabs next
to the variable names to allow them to be closed.

I didn't find a way to assemble windows in a way that split the main window
vertically, like this:

  |                   |
  |       var 1       |
  |                   |
  |                   |
  |       var 2       |
  |                   |

Is that possible?

Double clicking in an editor cell that contains a struct sub-element doesn't
open a new variable editor window for me.  Instead, nothing happens.  The same
for a sub-element that is a cell array.

Variables that can't be edited, like N-d arrays are no longer displayed.  All
I see is a variable editor window with a single empty cell.  Previously, these
were printed to a variable editor window.

Navigating in a variable editor window with the arrow keys no longer works for

Editing no longer works unless I double click in an editor cell first. 
Previously, I could navigate with the arrow keys and just type in a cell once
it was highlighted.  Double-clicking also worked to display the full value of
the cell, but it wasn't necessary to do that just to change a value.

With all these things, I don't think I can take this patch as it is.

It might be good to split out some of the hunks that just improve the
structure of the code and apply them separately, but I don't have time to do
that myself.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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