[AC-1072] Android Picker with column throws off index on device
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2014-04-23T04:53:24.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Titanium SDK & CLI |
| Labels | n/a |
| Reporter | Jayme Fishman |
| Assignee | Ritu Agrawal |
| Created | 2014-03-30T21:35:24.000+0000 |
| Updated | 2016-03-08T07:37:25.000+0000 |
Description
***NOTE: updated as this is also the case when using multiple columns ... not just single columns as originally reported. ***
Note: I will not be providing code to replicate this because it is very easy and occurs on the device - not the emulator - and there is a workaround:
1. Create a picker (useSpinner:true)
2. create a column
3. create a data array
4. iterate through array and call ti.ui.createPickerRow method.
5. add resultant object to column and add column to picker.
Symptom: none for Android emulator - works fine. On device: the single column throws off index of values by 1. It creates an extra value. When a row is selected from the getSelectedRow it will always return the row above it and you cannot select the top-most row (also there appears to be a blank row a the bottom). This does not impact the picker in non-spinner mode. Work-around: add data directly to picker and DO NOT use a column. Note: This is also different from iOS in which it will work fine. It seems to be an Android only device level issue that does not impact the emulator.
We need a simple runnable test case to reproduce this issue. I understand that you do not wish to provide a test case but we would have to close this ticket in absence of a test case.
Resolving this ticket as we cannot reproduce this issue and reporter has not provided a test case.