-
-
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
feat(linux): Allow loading of keyboards with arbitrary language 🏘️ #9735
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
c4f241e
to
2ae4953
Compare
2ae4953
to
3ec376f
Compare
2d3ca9d
to
b0dd74c
Compare
cust_kbd *kbd_data = (cust_kbd *)data; | ||
|
||
g_free(kbd_data->kb_id_with_lang); | ||
g_free(kbd_data->lang->id); |
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.
should we null check kbd_data->lang as well for safety?
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.
We always allocate kbd_data->lang
immediately after allocating kbd_data
, so I don't think there's a need for that. In fact, checking for kbd_data->lang->name
is unnecessary as well since g_free
will return if the parameter is NULL
.
`g_free` will return if the parameter is NULL, so we don't have to check for that. See glib [documentation](https://docs.gtk.org/glib/func.free.html).
Changes in this pull request will be available for download in Keyman version 17.0.192-alpha |
Part of #8598.
User tests will be part of the next PR that implements the necessary changes in keyman-config.
@keymanapp-test-bot skip