[Octave-bug-tracker] [bug #60469] F9 to run selected code stopped working

[Torsten Lilge]

Follow-up Comment #7, bug #60469 (project octave):

It looks like the connection of QScintilla's own signals is failing, among
them &octave_qscintilla::copyAvailable (causing this bug) or, e.g., signals
for indicating file mofification or updating line and row indicator in the
status bar.

When octave is started with the environment variable
"OCTAVE_SHOW_GUI_MESSAGES=1", there are altogether 13 occurrences of the error
message "QObject::connect: signal not found in octave::octave_qscintilla" for
each opened editor file.

Could the way how Qscintilla is linked to octave in the mxe build might
prevent the new signal/slot connection method from finding the signals?

    _______________________________________________________

Reply to this item at:

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

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