I've encountered this paradigm too and would also like to know why results can't be set as late as onPause? Hopefully somebody knowledgeable can chime in...
Having the differing behaviors between "confirm" and onPause() is causing pain because I want to have the "cancel" button act like confirm (the user is always saving unless explicitly clearing all fields or clicking a cancel/delete button) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
