[Octave-bug-tracker] [bug #47585] GUI editor does not show already active breakpoints when a file is opened

[Dan Sebald]

Follow-up Comment #14, bug #47585 (project octave):

Oh, you are using the file information from the command itself as a way to
direct the breakpoint information and avoid confusion:


  void file_editor_tab::update_breakpoints_handler (const octave_value_list&
argout)
  {
    octave_map dbg = argout(0).map_value ();
    octave_idx_type n_dbg = dbg.numel ();

    Cell file = dbg.contents ("file");
    Cell line = dbg.contents ("line");
    Cell cond = dbg.contents ("cond");

    for (octave_idx_type i = 0; i < n_dbg; i++)
      {
        if (file (i).string_value () == _file_name.toStdString ())
          do_breakpoint_marker (true, this, line (i).int_value (),
                                QString::fromStdString (cond (i).string_value
()));
      }
  }


Such a good construct, decomposing that "octave_map" and "contents".  This
fits together nicely.


    _______________________________________________________

Reply to this item at:

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

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