[TIMOB-2797] Ti.UI.currentTab is null
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2011-04-15T03:29:48.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Backlog |
| Components | Android |
| Labels | android, currenttab, ios, tab |
| Reporter | tom quas |
| Assignee | Don Thorp |
| Created | 2011-04-15T03:29:47.000+0000 |
| Updated | 2017-03-02T21:02:47.000+0000 |
Description
The Q&A section describes this pretty well.
http://developer.appcelerator.com/question/98501/titaniumuicurrenttab-is-null"> http://developer.appcelerator.com/question/98501/titaniumuicurrentt...
As James Wright mentioned, it should really be the job of the framework to handle this. Espeially, since you propagate the one-context approach in your documents. I'm running into this very problem today.
Related to #2786.
CurrentTab specifies the tab owning the window owning the context. That is, it's akin to currentWindow. The code sample in question is in app.js, which is not owned by any window, thus, no currentWindow, no currentTab.
Closed as invalid.