docs(indev): Document the relation between LV_INDEV_MODE_EVENT and data->continue_reading #5586
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
continue_reading
(feat(indev): in event-driven mode,needn'tcontinue_reading
#5363)")Commit 7e15886 disproves that continue_reading wasn't needed in event-driven mode.