[TIMOB-1014] iPad video problem

(from [c169b72f4ba19c85a5c0123aa0c51f97d4570998]) [#1014 state:invalid] Documentation change explaining that select/deselect annotation is not a valid operation unless the annotation is currently visible. http://github.com/appcelerator/titanium_mobile/commit/c169b72f4ba19c85a5c0123aa0c51f97d4570998"> http://github.com/appcelerator/titanium_mobile/commit/c169b72f4ba19...

Whoops! I tagged a submit with the wrong bug number. This is totally valid. That commit was for #1046.

Some investigation has revealed a number of issues with the media player we can't control:

• You may only have one movie view created at a time. Creating additional ones deallocates the view for any previously created players.
• Switching fullscreen mode automatically changes the scaling to 'Fit'. Any attempt on our (or the user's) part to change the scaling property when switching fullscreen causes playback to halt.

Lockup appears to be a combination of the multiple view issue, and something that was solved as part of #1044. After playing around with it for a while, there does not appear to be a good solution to the fullscreen scaling problem.

Leaving this open while I figure out what to do about multiple movie views.

(from [d83487ebd68c172869533791f9eb209bcee21b72]) [#1014 state:open] Fixes for views which seem to alleviate, but not solve, the drawing problem. http://github.com/appcelerator/titanium_mobile/commit/d83487ebd68c172869533791f9eb209bcee21b72"> http://github.com/appcelerator/titanium_mobile/commit/d83487ebd68c1...

More investigation into this bug reveals some hilarious peculiarities.

In particular, Apple allows for us to create two movies players, movie1 and movie2, and to add both of their views (in 3.2 & later) to the same window. However, only the view for the movie which was loaded LAST will respond and behave as though it is a view associated with a movie player controller, up to and including displaying the initial frame of a movie.

However, if we call -[MPMoviePlayerController play] programmatically, we can change which view is 'active'. So probably the best way to handle movie views in 3.2 when creating more than one at a time is to set the thumbnail from time 0.0 as the backgroundView, and set an event listener which responds to clicks on the view as a call to 'play'.

This is all going to have to happen to JS, unless we want to engage in a lot of reference counting of existing movie players and determine which one is currently active, etc. I'm marking this as resolved and will come up with a JS workaround for the helpdesk ticket mentioned above.

(from [e601fed72407f63cd7507882aabcd92812141b9d]) [#1014 state:resolved] Doc change to reflect video player weirdness. http://github.com/appcelerator/titanium_mobile/commit/e601fed72407f63cd7507882aabcd92812141b9d"> http://github.com/appcelerator/titanium_mobile/commit/e601fed72407f...