[Top][All Lists]

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

[Octave-patch-tracker] [patch #8316] Variable Editor

From: Rüdiger Sonderfeld
Subject: [Octave-patch-tracker] [patch #8316] Variable Editor
Date: Thu, 13 Feb 2014 20:53:56 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0


                 Summary: Variable Editor
                 Project: GNU Octave
            Submitted by: ruediger
            Submitted on: Thu 13 Feb 2014 08:53:55 PM GMT
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any



This patch adds a basic Variable Editor to the GUI.  It is not finished but I
wanted some input before continuing with it.

The biggest issue right now is that the editor does not detect changes
happening to the variable inside Octave.  It will continue displaying the old
value.  I don't know if there is a way in Octave to intercept changes to
certain variables or how this could be implemented.  The simplest way would be
to update the display completely once `octave_link::set_workspace' gets
called.  But this would only update the view when Octave has finished and is
waiting for new input.  Maybe that would be good enough at least for an
initial release.

There are some other issues

* Paste not working
* Inserting/removing rows/cols not working
* No support for structure arrays (completely untested)
* No subeditor opens for internal structures (but the input is eval'd so it is
somewhat usable at the moment)
* Plotting doesn't work for cell arrays.
* Delete does not support shifting and always inserts 0 (should be [] for cell
* No variable from selection or transpose feature
* No window splitting
* No data brush
* No printing
* No undo support
* No sort
* ...

And a potential thread safety issue.  I call `symbol_table::varval' in
`main_window' from the GUI thread to get the `octave_value'.  It could be
safely passed via signal but that would require registering `octave_value' as
Qt metatype and I don't know what implications that would have (See


File Attachments:

Date: Thu 13 Feb 2014 08:53:55 PM GMT  Name: variable-editor.patch  Size: 45kB
  By: ruediger



Reply to this item at:


  Message sent via/by Savannah

reply via email to

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