[Octave-bug-tracker] [bug #65339] Feature Request: Allow user to navigate the call stack in the gui

[Richard]

URL:
  <https://savannah.gnu.org/bugs/?65339>

                 Summary: Feature Request: Allow user to navigate the call
stack in the gui
                   Group: GNU Octave
               Submitter: crobar
               Submitted: Wed 21 Feb 2024 10:02:43 AM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 21 Feb 2024 10:02:43 AM UTC By: Richard <crobar>
When debugging in the GUI it would be useful to be able to navigate the
function stack, and have the editor reflect the current position in the stack.
This is done by other GUIs, for example, pycharm and the Matlab editor.

The editor should reflect changes to the call position made by the dbup and
dbdown commands. One way to get the information would be through the dbwhere
command, or it's internal implementation.

In terms of interface, it would be good to have a drop-down list that displays
the call stack, when you select the point in the stack from the list, the
corresponding file should be opened in the editor, and the debug line
indicator shown in the correct place.

Recent changes to dblist related to the following report might be useful in
helping someone to implement this in the future.

https://savannah.gnu.org/bugs/?65330







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65339>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/