I should have been more specific ... this is for an iPhone app which to me says UIPickerView cannot be visible always because of it ponderous size.
-koko On Apr 26, 2011, at 3:51 PM, glenn andreas wrote: > > On Apr 26, 2011, at 4:36 PM, koko wrote: > >> So we have one vote for: >> >> 3. Use a view in a layer of the current view >> >> Any other views (no pun intended) ... going once going twice .... >> >> Any comments against : >> >> 1. Use UIAlert - easy but seems clunky >> >> -koko > > > Adding additional content in UIAlert is not recommended, since it requires a > high degree of care and verges on something that can get an app rejected from > the App Store. (you've got to do special casing for different versions of the > OS and make bad assumptions about the layout of the subviews, and will quite > likely break when the next OS release happens). > > In general, if you can avoid making a UIPickerView "appear" as the result of > an action, you'll be better off. Make it part of the UI, always available, > or use a different mechanism (for example, in a table view, just push a > second table view onto the navigation controller and let the user select the > element from that table view, just like Settings.app does, etc...) > > > > Glenn Andreas gandr...@gandreas.com > The most merciful thing in the world ... is the inability of the human mind > to correlate all its contents - HPL > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
