Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
CacheUpdate
|
|
CacheUpdate
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CacheUpdate
|
|
|
|
If nextSetup is true, then the media player has already called setNextMediaPlayer. Since this is already inside of the onCompletion, there is a pretty good chance that the next media player is already playing. In this case we can't risk going into the condition where the current media player will be restarted.
|
|
starters
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
uncancellable, thus unusable for my purposes
|
|
|
|
interrupt was called during a non-blocking action
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The old implementation only kept current + 1 old drawable. While this reduced the number of cases where the old drawable was attempted to be used, it did not completely eliminate it. There were still cases where the + 1 old drawable was used and caused a crash. This new implementation just completely clears the old transition drawable from the stack after a certain amount of time.
|