Oh, another bug I thought I saw posted about the feeds, but after looking back, I don't see it mentioned by anyone, so while we're piling on the feeds here... Anyone else seeing this one?
I put the feed on a rectangle. Great, works good (as long as something else is updating on screen of course, otherwise the feed never updates -- already discovered). Put poverlays on top, works great. Mask the feed object, works great. Everything works great... Until.
The user changes screens, and I call display:remove() or object:removeSelf(). Shortly I release() the screen that had the feed (and construct/display the new screen), I get a hard crash on iOS -- "Bus Error: 10".
I had tried several ways to disengage the feed from the OS before the remove() (like setting isVisible = false, setting.fill = "" / nil, using a timer.delay to allow the graphics update, etc), but couldn't isolate a method that would get around it... So I switched to the "if you can't beat them, join them" strategy again (like for the other bug, just keep something moving)...
To prevent the crash (actually to prevent the removal of the feed), when the screen with the feed exits it now creates a global feedgroup and inserts the feed rect into it, then places the group object WAY offscreen so it wont be seen, makes it invisible, etc. (Next time it reloads it checks if the feed already exists, and re-uses it).
With both bugs (feed not updating, and the bus error bug), I've got more workaround code than I'd like, but hey, I'm still moving forward onto more screens.
Anyways -- anyone else seeing bus error 10: when removing your feed yet?