[TIMOB-2536] Android: Activity lifecycle events should be synchronous callbacks
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Low |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:59:23.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M05 |
| Components | Android |
| Labels | activity, android, feature, release-1.6.0 |
| Reporter | Marshall Culpepper |
| Assignee | Marshall Culpepper |
| Created | 2011-04-15T03:22:08.000+0000 |
| Updated | 2011-04-17T01:59:23.000+0000 |
Description
The current "create", "pause", "resume", "destroy", etc lifecycle events on ActivityProxy should be made into synchronous callbacks so apps can participate in the lifecycle
(from [98daa90a4b953f3b092cab41a7ab49c30d6d49fd]) expose an API to fire events synchronously, fire all Activity lifecycle events sync, and expose Activity.finish() [#2536 state:fixed-in-qa]
https://github.com/appcelerator/titanium_mobile/commit/98daa90a4b953f3b092cab41a7ab49c30d6d49fd"> https://github.com/appcelerator/titanium_mobile/commit/98daa90a4b95...
Marshall says no easy way to test, moving along