Open GoogleCodeExporter opened 9 years ago
The reason it doesn't already exist is because start a movie is a lot of
actions, such as closing a game, and clearing out tools, loading the rom again,
setting tools back up, creating a new core instance, stopping any existing
movie, starting a new movie instance, and a lot of complicated things have to
be considered.
The movie library isn't capable of doing most of this work either since there's
a lot of client specific work to do there. I could do a client.start(...) but
that seems weird and unclean, so I don't know.
Original comment by adeli...@tasvideos.org
on 6 Mar 2015 at 12:33
I see, that makes sense. In that case, is a movie.save(...) or some other
function that forces a write of the current movie possible? As best as I can
tell, the active movie is only present in memory and doesn't get written to
file until the movie is stopped.
Original comment by omni.koz...@gmail.com
on 6 Mar 2015 at 12:47
Original issue reported on code.google.com by
omni.koz...@gmail.com
on 1 Feb 2015 at 5:00