[EPG] Fix gap tag update handling. #11971
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ksooo
added
Backport: Needed
Type: Fix
|
jenkins build this please |
|
jenkins error is unrelated. (FATAL: Could not checkout e1b196d) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a followup to #11879, where so called gap tags ('holes' in the epg) were not handled correctly. Effect was 'jumping' epg grid after selecting a gap tag followed by some time of user inactivity (hard to explain, but easy to spot :-).
The changes were runtime tested on macOS, latest Kodi master.
Needs backport.
@Jalle19 mind doing the code review.