{ "id": "61953", "key": "TIMOB-1321", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "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": "11239", "name": "Release 1.6.0 M06", "archived": true, "released": true, "releaseDate": "2011-01-24" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:55:51.000+0000", "created": "2011-04-15T02:49:19.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "android", "feature", "release-1.6.0" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:55:51.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}
When an OptionDialog is created, there is no way to set which of\nthe options in the list is currently active. This is a behaviour\nthat is seen throughout many apps in the android marketplace. The\nsettings in the Alarm Clock (installed by default on Android\ndevices) is an example of this.
\nPlease see \nhttp://developer.appcelerator.com/question/43591/how-to-set-default...\nfor more information.
\nThanks
\nHal
I difficult to understand why option dialog does not have an\n\"enabled\" property, like the switch control.
Just to note, while I still think it would be logical to have\nthis feature in optionDialog, for those who require this feature on\nAndroid, investigate the Ti.UI.createPicker() control.
I talked with the iOS folks and OptionDialog is intended to be\nused as a set of \"buttons\" non-stateful selection. We will need to\ncreate another control for Android that supports persistent\noptions. Once we figure that out. I'll change the title of the\nissue to reflect that task.
Added the ability to specify the selectedIndex when the Dialog\nis created: https://github.com/appcelerator/titanium_mobile/pull/54
Moving to M06. Ran out of time to document and write test code\nin M05.
(from [dab7f412915b60ea29fa225db3a3bea5ad6df356])\n[#1321 state:fixed-in-qa] documented, KS updated\nto use selectedIndex, fixed bug in patch, added support for\nproperty changes. \nhttps://github.com/appcelerator/titanium_mobile/commit/dab7f412915b...
(from [10496792a725d70330aaae406bd0e2610ee2e3d3])\n[#1321 state:in-progress] code, needs test and\ndoc. Merge branch '1321-defaultOptionUIOptionDialog' of https://github.com/yellowandy/titanium_mobile\ninto yellowandy-1321-defaultOptionUIOptionDialog \nhttps://github.com/appcelerator/titanium_mobile/commit/10496792a725...
out of order notification changed this back to in-progress. Hand\nsetting it to fixed-in-qa.
verified with KS on Nexus S / 2.3.2