[Octave-bug-tracker] [bug #57220] Ctrl+C does not interrupt loops or demo sessions anymore

[John W. Eaton]

Follow-up Comment #9, bug #57220 (project octave):

The default value for sc_main_edit_copy is currently set to QVariant
(QKeySequence::Copy), not QVariant ("Ctrl+C").

If I understand correctly, QKeySequence::Copy is an enum value (== 9).  If you
store that in a QVariant object and then use toString directly on that
QVariant object without first extracting the value as a QKeySequence object, I
think you will get QString("9"), not QString("Ctrl+C").

If we want to work with strings, then shouldn't we be setting the default as
"Ctrl+C" (or converting QKeySequence::Copy to its string representation)?

If the settings file contains strings like "Ctrl+C", are they converted to
QKeySequence objects when they are read or kept internally as QString
objects?

Also, looking at the QTerminal sources, has_extra_interrupt is a bit confusing
by itself, at least to me.  Maybe there is a better name for that, or some
better way to express what is intended?  It seems that has_extra_interrupt
(true) means that that the shortcuts for Copy and Interrupt are different.

    _______________________________________________________

Reply to this item at:

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

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