"EnTerr" wrote:"TheEndless" wrote:
"soon" with firmware updates could be weeks or even months, so you may want to look into adding your own looping functionality. It's easy enough to listen for the isFullResult() event and restart the stream.
One would think breaking a long-existing, long-documented function - that setLoop() apparently is - creates some urge to fix it.
Are app review times shorter than bugfix pushes to firmware?
Also, is isFullResult() less likely to break down than setLoop()? (I.e. what happens if next firmware fixes setLoop but breaks isFullResuit ...)
So I did what you said TheEndless and the looping seems even smoother than when I use the built in function lol. Thanks again.