Skip to content
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

docs(indev): Document the relation between LV_INDEV_MODE_EVENT and data->continue_reading #5586

Merged
merged 1 commit into from Feb 5, 2024

Conversation

neuschaefer
Copy link
Contributor

This relation was introduced but not documented in commit 1881ef2 ("feat(indev): in event-driven mode,needn't continue_reading (#5363)").


The alternative and simpler approach would be to respect data->continue_reading unconditionally. Input devices that don't want to trigger the looping logic should simply never set continue_reading then. The following commits could be reverted:

Commit 7e15886 disproves that continue_reading wasn't needed in event-driven mode.

…ta->continue_reading

This relation was introduced but not documented in commit 1881ef2
("feat(indev): in event-driven mode,needn't `continue_reading` (lvgl#5363)").


The alternative and simpler approach would be to respect
data->continue_reading unconditionally. Input devices that don't want to
trigger the looping logic should simply never set continue_reading then.
The following commits could be reverted:

- commit 7e15886 ("fix(sdl): fix keyboard handling (lvgl#5575)")
- commit 1881ef2 ("feat(indev): in event-driven mode,needn't `continue_reading` (lvgl#5363)")

Commit 7e15886 disproves that continue_reading wasn't needed in
event-driven mode.
@FASTSHIFT FASTSHIFT merged commit c23b9bc into lvgl:master Feb 5, 2024
16 checks passed
kisvegabor pushed a commit that referenced this pull request Feb 5, 2024
kisvegabor pushed a commit to kisvegabor/lvgl_upstream that referenced this pull request Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants