{ "id": "61646", "key": "TIMOB-1014", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11224", "name": "Release 1.4.0", "archived": true, "released": true, "releaseDate": "2010-07-16" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:54:57.000+0000", "created": "2011-04-15T02:41:31.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "blainhamon", "key": "blainhamon", "displayName": "Blain Hamon", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:54:57.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
see http://helpdesk.appcelerator.net/tickets/2662
\ntest case is attached to the ticket.
(from [c169b72f4ba19c85a5c0123aa0c51f97d4570998])\n[#1014 state:invalid] Documentation change\nexplaining that select/deselect annotation is not a valid operation\nunless the annotation is currently visible. \nhttp://github.com/appcelerator/titanium_mobile/commit/c169b72f4ba19...
Whoops! I tagged a submit with the wrong bug number. This is\ntotally valid. That commit was for #1046.
Some investigation has revealed a number of issues with the\nmedia player we can't control:
\nLockup appears to be a combination of the multiple view issue,\nand something that was solved as part of #1044.\nAfter playing around with it for a while, there does not appear to\nbe a good solution to the fullscreen scaling problem.
\nLeaving this open while I figure out what to do about multiple\nmovie views.
(from [d83487ebd68c172869533791f9eb209bcee21b72])\n[#1014 state:open] Fixes for views which seem to\nalleviate, but not solve, the drawing problem. \nhttp://github.com/appcelerator/titanium_mobile/commit/d83487ebd68c1...
More investigation into this bug reveals some hilarious\npeculiarities.
\nIn particular, Apple allows for us to create two movies players,\nmovie1 and movie2, and to add both of their views (in 3.2 &\nlater) to the same window. However, only the view for the movie\nwhich was loaded LAST will respond and behave as though it is a\nview associated with a movie player controller, up to and including\ndisplaying the initial frame of a movie.
\nHowever, if we call -[MPMoviePlayerController play]\nprogrammatically, we can change which view is 'active'. So probably\nthe best way to handle movie views in 3.2 when creating more than\none at a time is to set the thumbnail from time 0.0 as the\nbackgroundView, and set an event listener which responds to clicks\non the view as a call to 'play'.
\nThis is all going to have to happen to JS, unless we want to\nengage in a lot of reference counting of existing movie players and\ndetermine which one is currently active, etc. I'm marking this as\nresolved and will come up with a JS workaround for the helpdesk\nticket mentioned above.
(from [e601fed72407f63cd7507882aabcd92812141b9d])\n[#1014 state:resolved] Doc change to reflect\nvideo player weirdness. \nhttp://github.com/appcelerator/titanium_mobile/commit/e601fed72407f...