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

feat(indev): in event-driven mode,needn't continue_reading #5363

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

bjsylvia
Copy link
Contributor

Help us review this PR! Anyone can approve it or request changes.

Description of the feature or fix

A clear and concise description of what the bug or new feature is.

Checkpoints

src/indev/lv_indev.c Outdated Show resolved Hide resolved
…ot required

Signed-off-by: YanXiaowei <yanxiaowei@xiaomi.com>
@bjsylvia bjsylvia force-pushed the feat-indev-read-event branch from 53518d2 to d9d73d2 Compare January 18, 2024 01:32
@bjsylvia bjsylvia requested a review from kisvegabor January 18, 2024 01:49
@kisvegabor kisvegabor merged commit 1881ef2 into lvgl:master Jan 18, 2024
16 checks passed
kisvegabor added a commit to kisvegabor/lvgl_fork that referenced this pull request Feb 2, 2024
neuschaefer added a commit to neuschaefer/lvgl that referenced this pull request Feb 4, 2024
…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.
@bjsylvia bjsylvia deleted the feat-indev-read-event branch December 18, 2024 22:58
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.

4 participants