[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #65797] adding keyboard command within __bar__
|
From: |
Nicholas Jankowski |
|
Subject: |
[Octave-bug-tracker] [bug #65797] adding keyboard command within __bar__.m update_data() function causes Octave hang |
|
Date: |
Mon, 27 May 2024 15:34:06 -0400 (EDT) |
Follow-up Comment #2, bug #65797 (group octave):
Ok, this sounds like its not windows specific, so I'll update the tags. If
the summary can be appropriately broadened please do so.
in the context of my current debugging of the bar subfunctions, is there any
logic to why the two keyboard positions behaved so differently? Should I just
avoid using keyboard in the bar subfunctions? I haven't always beena able to
consistently get regular breakpoints in private functions to behave, and not
sure how else to check the listeners on the bar object properties.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65797>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/