On 10 Jan., 22:21, Kumar Bibek <[email protected]> wrote: > The reason why a NumberPicker is not public or a part of the SDK is > perhaps because it's not a widely used widget. If it were, it would > have been a part of the SDK, and the widget would have been public. > IMO.
I think it's more like the other way around: It's not widely used because it's not public. Well, and maybe partly because it's not that beautiful and somewhat buggy (esp. if you enter numbers with the keyboard). Nontheless, I think you'd see it way more often if it was easier to use in own apps, and esp. if there would be support in preference views - I for one often would prefer a number picker to lists of predefined values or SeekBars, which are terribly imprecise. (Dear Android developers: if you'd really do that, please also offer min and max values) > There might be other reasons as well, but this seems to be the most > obvious reason. Remember, the SDK is for a mobile device. I don't see why this should matter. The NumberPicker already is used for date and time pickers since several Android versions on as "weak" mobile devices as G1 or Tattoo. And I think even those would also cope quite fine with somewhat fancier variations like the digit wheels shown in the original post. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
