Closed Johennes closed 1 year ago
Thanks for the fix! :+1:
BTW, now LVGL master
has the new architecture and we can add the drivers from this repo. This way we'd have a lot of drivers in a central place, and they would be versioned and maintained together.
You you be interested in contributing by moving this driver to LVGL master
? Here is a summary about the changes.
BTW, now LVGL
master
has the new architecture and we can add the drivers from this repo. This way we'd have a lot of drivers in a central place, and they would be versioned and maintained together.You you be interested in contributing by moving this driver to LVGL
master
? Here is a summary about the changes
Oh, great! Having them in a single repository would also make the packaging a bit easier for us. We're currently investigating keys being dropped when typing too fast with the current libinput driver (https://gitlab.com/cherrypicker/unl0kr/-/issues/36). Looks like switching to the new driver architecture on LVGL master
would be a good next step before we dive deeper into this. :+1:
Happy to hear that you are interested in it! :relaxed:
Let me know when you'd like to jump into it and need some assistance.
This leak was reported by Valgrind in unl0kr (see https://gitlab.com/cherrypicker/unl0kr/-/issues/43). It turns out that
xkb_keymap_new
andxkb_state_new
return referenced instances. So the extra calls toxkb_keymap_ref
andxkb_state_ref
were not needed and caused the memory to not be properly cleaned up inxkb_deinit_state
.Apologies for introducing this bug together with the original XKB work in lv_drivers. I was mistakenly assuming this was the correct way to use the API because the libinput API worked this way.