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

[John W. Eaton]

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

I guess I'm confused about what the intent of that bit of code is.  To avoid
more confusion in the future, can we explain it clearly in the comments
there?

Also, it doesn't seem correct to me to convert a key sequence to a string and
then back to a key sequence.  That's why I made the change to use the default
value for sc_main_edit_copy (QKeySequence::Copy) and extract a QKeySequence
from the QVariant object returned by the settings->value function.

If you take an arbitrary QKeySequence value, store it in a QVariant object,
extract it as a string, then convert it to a QKeySequence, is it guaranteed
that you will recover the original QKeySequence value?  Even if that is true,
it seems somewhat strange to me to do that series of conversions.

    _______________________________________________________

Reply to this item at:

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

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