The other key point is that generally our model is for data to be edit-in-place, so pressing back from something like contacts will close the screen but retain your edits (since the edits were performed as you did them).
There will always be exceptions -- I think gmail confirming you want to cancel your message if you haven't yet saved it as a draft is a good one because otherwise you unintentionally end up with a lot of drafts -- but what you see in contacts is the general model. We do need to get UI guidelines out that describe all of this in much more detail. I know this has been an issue for a while. Btw, the scenario of editing a contact and removing all data then pressing back is an edge case that to me is consistent with the model -- the contact has no more data, so it no longer exists. When you press back you have already made the edits that make it empty so it is now gone. On Thu, Sep 17, 2009 at 1:04 PM, niko20 <[email protected]> wrote: > > > Hi, > > The back button is really not meant to be "cancel" usually, but only > to exit the current screen you are working on. > > -niko > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
