{ "id": "61187", "key": "TIMOB-555", "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": "11226", "name": "Release 1.5.0 M01", "archived": true, "released": true, "releaseDate": "2010-11-15" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:53:30.000+0000", "created": "2011-04-15T02:31:46.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "blur", "defect", "focus", "tabGroup", "tabgroup" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:53:30.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": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
The tabchange event comes long after the focus/blur occurs. This\nwasn't a problem before 0.9 because tabchange was separate from\nfocus/blur.
valid, has testcase
Is there any chance this will be fixed soon?
A nasty hack for this problem. It works for me for 99%:
\n\ntabGroup.addEventListener('focus', function(e)\n{\n setTimeout(function()\n { \n Ti.API.debug('tab changed to ' + tabGroup.activeTab); \n },100);\n});
\n
Pass Titanium SDK version: 1.5.0 (12/01/10 09:30 ac7cfd8)\nKitchenSink, Android 1.6 Device, 2.1 Sim
is this bug fixed? please provide a alternative to this problem\nif not fixed.
I would like to know if is this bug fixed? please provide an\nalternative to this problem if not fixed.
It's in a resolved state, so yes it's fixed.