Fixed double-start bug in refreshNextTimer.
This commit is contained in:
parent
dcafd8faf6
commit
e34dcbdec7
|
|
@ -287,10 +287,8 @@ module.exports = class{
|
||||||
if(currentItem != null && (this.nowPlaying == null || currentItem.uuid != this.nowPlaying.uuid)){
|
if(currentItem != null && (this.nowPlaying == null || currentItem.uuid != this.nowPlaying.uuid)){
|
||||||
//Start the found item at w/ a pre-calculated time stamp to reflect the given start time
|
//Start the found item at w/ a pre-calculated time stamp to reflect the given start time
|
||||||
this.start(currentItem, Math.round((new Date().getTime() - currentItem.startTime) / 1000) + currentItem.startTimeStamp, volatile);
|
this.start(currentItem, Math.round((new Date().getTime() - currentItem.startTime) / 1000) + currentItem.startTimeStamp, volatile);
|
||||||
}
|
|
||||||
|
|
||||||
//If we have a next item
|
//If we have a next item
|
||||||
if(nextItem != null){
|
}else if(nextItem != null){
|
||||||
//Calculate the amount of time in ms that the next item will start in
|
//Calculate the amount of time in ms that the next item will start in
|
||||||
const startsIn = nextItem.startTime - new Date().getTime();
|
const startsIn = nextItem.startTime - new Date().getTime();
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue