ryanheise

I know that people are using that workaround successfully (lazily adding items to the playlist just-in-time so that you don't try to load them all at once). I suggest you...

@pro100svitlo 's approach should work, it's a treadmill with always 3 items. I'm not going to implement it here @mhutshow but @pro100svitlo has given the pseudocode in his previous comment....

@mirkancal What are you referring to by the word "it"? Do you mean one of the workarounds or pseudocode mentioned above, and if so, which one?

I am recently considering implementing the treadmill approach within the Dart side of the plugin, and that would involve removing the existing Android implementation which is currently implemented entirely on...

Hmm, while this idea is attractive at first glance, I just spent a little time thinking about how I would implement this approach and I don't think it would be...

I have just implemented an iOS/macOS treadmill. It is available for testing on the `feature/treadmill` branch. Currently it is hard coded to be always on because it is actually difficult...

It took me 1.5 years to find a quick solution :-) But even still I dreaded changing the iOS queuing logic since it was complex to write the first version...

As stated above, that approach will not work due to the way the platform interface works. However, with the current API it is completely possible for an app to implement...

Is anyone able to report on their experience with the solution implemented in `feature/treadmill`? As mentioned, I am reluctant to merge changes to this core code unless people find that...

Does this happen for you on `example_playlist.dart`?