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

[John W. Eaton]

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

I did some checking and it works for me if I use the following pattern with
the new signal/slot connection method:


    connect (dynamic_cast<QsciScintilla*> (m_edit_area),
             &QsciScintilla::copyAvailable,
             this, &file_editor_tab::handle_copy_available);


for the signals that are emitted from the base QsciScintilla object itself.

As noted earlier, this problem only occurs on Windows systems.  Is it related
to the way pointers are handled in DLLs?  Or is it just a difference in the
way pointers are handled in a class like this where signals are inherited? 
I'm not sure whether it is the connection or the execution of the signal/slot
connection that fails.

I suppose it is good that there is a way to use the new signal/slot syntax in
this case, but it seems quite bad to me that there is no warning for an
inherited signal like this.


    _______________________________________________________

Reply to this item at:

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

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