[pvr] match EPG tag pointers when associating timers with events #7242
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
…er and an EPG tag Some backends may consider recordings to have started when the actual recording started, not when the recorded programme starts. This means the start time differs and the timer/recording cannot be matched with the corresponding EPG tag.
|
Looks sane to me. |
|
+1 jenkins build this please |
Jalle19
added a commit
that referenced
this pull request
Jun 8, 2015
[pvr] match EPG tag pointers when associating timers with events
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.
Some backends may consider a recording to have started when the actual recording
started, not when the recorded programme starts. This means the start time differs and the timer/recording cannot be matched with the corresponding EPG tag.
For backends that provide a link between EPG tags and timers this also implies a minor speedup since the various comparisons are skipped if a matching pointer is found.
@opdenkamp @ksooo @xhaggi can we include this for Isengard? I can't really work around this in the addon.