Bill - I don't know if my Helpdesk request #92651\n(android-picker-wspinner-limited-to-3-columns) is included in this\nor the other picker request items, but wanted to put it out there,\nFYI. We have an iOS app that uses 4 columns - ideal for getting\nmaximum screen real estate use for user input out of the Picker,\nesp. when the values of each field are relatively limited in range.\nI would think 5 columns would be a reasonable limit. I do hope that\nthe limit of 3 can be lifted in the 1.6 release(?).
There is no limit of 3 (you might think that because it's only\nshowing three due to its inability to have column widths applied to\nit.)
\nFor example:
\n\n/*global Ti, Titanium, alert, JSON, require, setTimeout, setInterval */\nTitanium.UI.setBackgroundColor('#000');\nvar win = Titanium.UI.createWindow({ \n title:'Test',\n backgroundColor:'#000',\n exitOnClose: true\n});\n\nvar columns = [];\nfor (var i = 0; i < 7; i++) {\n var rows = [];\n for (var j = 0; j < 3; j++) {\n rows.push(Ti.UI.createPickerRow({title:'x'}));\n }\n columns.push(Ti.UI.createPickerColumn({rows:rows}));\n}\nwin.add(Ti.UI.createPicker({\n type: Ti.UI.PICKER_TYPE_PLAIN,\n useSpinner: true,\n columns:columns\n}));\n\nwin.open();\n\nThat will easily show 7 columns on a 320 width screen. But it's\nalso pretty useless. :)
\nBut yeah, this is exactly the kind of thing I'm working on: the\nability to set column dimensions and such, so you can control how\nit takes up real estate.
So if I remove the explicit widths, should my app show 4\ncolumns? Not sure why the widths are so large now if it ignores\nwhat I provided...? (The contents are not that wide.) Also, will\nthe current version pay attention to font size?
(from [be86230d6ee9c657c39326efcd04a1d3154d9c7c])\n[#2365] First push of re-factored spinner. Still\nneed to apply styles/dimensions. \nhttps://github.com/appcelerator/titanium_mobile/commit/be86230d6ee9...
(from [30b41a3a4fa5693555afca3c91ca7824eb508dfb])\n[#2365 state:fixed-in-qa] support font/text\nattributes in spinner, as well as removing columns and replacing\nrows in existing columns. \nhttps://github.com/appcelerator/titanium_mobile/commit/30b41a3a4fa5...
The test for this is in KitchenSink: Controls -> Picker ->\nAndroid \"useSpinner\" - text (2). It shows a few examples such as\nsetting font characteristics and explicit column widths.
(from [58d6da5d262768bbe1273c880df98b9a22a29cf4])\n[#2365] update the 'Android useSpinner text (2)'\ntest to show the new selectionIndicator property \nhttps://github.com/appcelerator/titanium_mobile/commit/58d6da5d2627...
(from [acf463c9ab59d42d25f0d166e2bfa39caf7a7873])\n[#2365] Also support the documented\nselectionIndicator property and move property change handling to\nthe views as we usually do. \nhttps://github.com/appcelerator/titanium_mobile/commit/acf463c9ab59...
verified on droid2 2.2
(from [3e6469ab5a206d255d5b3f45d696a3a000063a77])\n[#2365 state:fixed-in-qa] Handle required\nre-layout when visibleItems or font characteristics changed after\nalready layed out. \nhttps://github.com/appcelerator/titanium_mobile/commit/3e6469ab5a20...
verified again on emulator 2.2
Bill - the latest builds of 1.6.0 (Feb 16) show that custom\nattributes for picker rows are not supported in the Android picker\n- they simply are not accessible. This greatly reduces the utility\nof the picker if you cannot provide formatted data whose native\nvalue or code is not accessible from the event handler object. See\npicker_basic.js in the Kitchen Sink - custom_item value is always\nundefined in Android; works in iOS. Would love to know if this is\nan easy fix likely to make the 1.6.0 release?
Also - is there any doc on using fonts and other attributes for\nthe Android picker? The online API docs seem to indicate that\nfontSize is supported, but that has no effect; the doc page also\nshows \"font-size\", \"font-weight\", and \"font-family\" - are these\nsupported at all? Is there an ability to control the height of the\npicker itself (e.g., you want 5 rows shown but in a larger\nsize)?