DonFrench wrote: > I was surprised and dismayed to discover that the DatePicker and > TimePicker classes, which are of parallel construction in almost every > way, differ in one significant way. There is no > setOnDateChangedListener(...) method in DatePicker while there is a > setOnTimeChangedListener(...) method in TimePicker. For two classes > that parallel one another in every other way, including the appearance > and operation of their corresponding Views, why do they diverge in > this fairly important aspect? I eventually discovered that there is > a way to set the OnDateListener through the init(...) method, but COME > ON! Was this just an oversight on Google's part? I hope that they > fix this in a coming release.
This was requested as an enhancement request about a year ago: http://code.google.com/p/android/issues/detail?id=2006 If it is important to you, you are welcome to make a patch and submit it for inclusion in an upcoming release. Or, perhaps just star that issue, since at present, virtually nobody else seems to care about it, so it is not likely to be dealt with any time soon. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training in US: 14-18 June 2010: http://bignerdranch.com -- 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
