Hi, We would be interested in other's feedback on this one. It is certainly possible, we sometimes find Open/Cancel buttons can get in the way and reduce efficiency, however we are happy to consider it if the consensus is it is better. Jess
I agree with the above, I found it a little awkward to tap away to confirm—I would prefer an "Okay/Cancel" option, so the process to confirm or cancel is clearer.
It's the lack of feedback when you select a date. Other datepickers I use either close the date picker when you click on a date or they have okay/cancel. Thanks for considering the change though!
We didn't want to close the picker straight away when setting a date, because you may then want to tap and set the end date also. Plus, I rarely set the exact date I intend straight away, I tend to tap around as I think, so having it collapse on me would be a pain. And I have always found the UX of date range lickers where first tap = start date, second tap = end date to be frustrating, because I often only want to change one of the values. That option is simply too destructive and unwieldy here, as you may accidentally change important info, and the start and end dates may be very far apart. Which led us to our design choice. The Okay/Cancel buttons are an alternative to consider. Is tapping away to close that unusual? That is how the Entity lists behave also, as an example. Does the date picker feel different to that somehow?
I just realised how the entity dates work. Hitting "Back" to confirm a value is definitely not something I'm used to. I'm used to confirming any action with an affirmative. But I'm just one person and other folks may definitely have other opinions. I agree about the double tap for start and end dates. It's very easy to get into a situation where you select the wrong date for the start and then have to go through the cycle again.
Eek, just re-read my previous comment. For future reference people, I meant Date Range *pickers* :-)
When I referred to entity lists above though, I meant the list of roles in the Inspector - e.g. Adding Participants, Characters etc. where you can have multiple. I probably agree that any decision on OK/Cancel for the date picker should be replicated in each place a Date Picker lives.