Affects Version/s: Release 7.1.1
Fix Version/s: Release 7.3.0
Name = Microsoft Windows 10 Pro
Version = 10.0.16299
Architecture = 32bit
- CPUs = 4
Memory = 17091956736
Node.js Version = 8.9.1
npm Version = 5.5.1
CLI Version = 5.1.0
SDK Version = 7.1.1.GA
- CPUs = 4
Sprint:2018 Sprint 11 SDK
We have having issues related to disabling the children of Ti.View. If we make touchEnabled false for a View, it does not make its children uneditable.
Where as if we use Ti.ScrollView instead, everything is working as expected.
As mentioned in the ticket TIMOB-25306, since we can not make the picker disabled by setting its touchEnabled property as false, we are trying to use it as a workaround to disable its Parent view which would in turn disable all its children.
Steps to reproduce:
1. Run the attached Alloy project TestPickerDisabled
2. You can see two Pickers and two TextFields. Picker and TextField whose background color is yellow are children of Ti.View where as the other Picker and TextField whose background color is Red are children of Ti.ScrollView.
3. We have touch enabled property set to false for both Ti.View and Ti.ScrollView. You can observe that the Picker and the TextField that are children of Ti.View are editable where as the children of Ti.ScrollView are not editable.
Test Project : TestPickerDisable.zip
Test Environment :