-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(developer): handle KM_CORE_IT_INVALIDATE_CONTEXT
in debugger
#11488
fix(developer): handle KM_CORE_IT_INVALIDATE_CONTEXT
in debugger
#11488
Conversation
User Test ResultsTest specification and instructions Test Artifacts
|
KM_CORE_IT_INVALIDATE_CONTEXT
in debugger
@@ -360,6 +360,13 @@ function TDebugEventList.AddStateItems( | |||
|
|||
AddDebugItem(debug, debugkeyboard, vk, modifier_state); | |||
|
|||
if action._type = KM_CORE_IT_INVALIDATE_CONTEXT then | |||
begin | |||
// We always ignore invalidate context which can come when a frame key is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.
Is this the same behavior on a non-debug event?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the debugger specifically ignores the invalidate context event because it always tracks the context, including markers. It's the only app that ever knows about markers, so it's the only app that can ignore the event.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Test Results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
post merge LGTM
"I ignore invalidate context" could be part of the core API but probably not needed.
Changes in this pull request will be available for download in Keyman version 18.0.41-alpha |
The output from Keyman Core changed in #11172 to emit a
KM_CORE_IT_INVALIDATE_CONTEXT
action when a frame key is pressed, but the debugger was not catering for this scenario, causing an assertion failure.Fixes: #11486
Fixes: KEYMAN-DEVELOPER-1Y4
User Testing
TEST_DEBUGGER_KEYS: In the Keyman Developer debugger window, press a variety of keys, including letter keys, arrow keys, and more. The debugger should no longer crash.