Yes, it is made null in the onSuccess function. In 1.4.1 this works (causes/lets everything function normally) but in 1.5.0..
My theory is that the mediaSuccess (callback, optional) is no longer as described in this quote from docs: mediaSuccess: (Optional) The callback that is invoked after a Media object has completed the current play/record or stop action. is being called IMMEDIATELY upon successful play (in my example), and NOT called AFTER it has "completed the current play/record or stop action". So my initial implementation of onSuccess (like 'mediaSuccess' above) was as a cleaner-upper, as I assumed it would be called strictly after completion of .play(). Seems the current implementation makes mediaSuccess an async confirmation that the play has succeeded. Not sure if this is important, docs updated later etc, just adding my interpretation of the diff between 1.4.1 and 1.5. Libby On Thu, Mar 1, 2012 at 11:59 AM, Simon MacDonald <simon.macdon...@gmail.com>wrote: > On Thu, Mar 1, 2012 at 12:57 PM, Elizabeth Baldwin > <libby.bald...@gmail.com> wrote: > > > > Media: Can access and play mp3, BUT current position always -1 ? , can't > > pause or stop. > > Live Record/Playback: still OK > > I'm not sure why but it seems like once you are out of "playAudio" the > variable "my_media" is always null. Don't ask me why as this code is > nearly the same as what we have in mobile-spec but I don't have time > to debug it right now. > > Simon Mac Donald > http://hi.im/simonmacdonald >
