Why can't Datepicker dialog automatically figure out that there are no 30 and 31 in Feb? Should not this be considered as a bug in DatePicker class?
The DatePicker dialog's 'set' button can be pushed without telling user 'this is an invalid date' -- instead, it quietly convert 4/31 to 5/1; 2/30 to 3/2 after you push the button. I think an idea behavior should be as following: -- when you currently have "1 31 2009" and push the 'up' button on '1' (month), you should get "2 28 2009" shown on the three elements I thought to build a customized subclass, but a lot of the fields are private and not accessible from subclass, anyone thought of the same problem? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
