User Lost Data Input because of Activity Dialog Functionality

[GoogleCodeExporter]

User was adding a new rule, chose event, added an email action, decided they 
wanted to change something and hit "back" which goes back to "ChooseRootEvent" 
resulting in loss of all data entered which was frustrating.  We could consider 
using actual full activities and add each to the stack until "Save" occurs and 
then clear the activity stack to avoid such a loss.  Not sure if this is a good 
approach.

Original issue reported on code.google.com by case.and...@gmail.com on 2 Aug 2010 at 12:15

• Merged into: #115

[GoogleCodeExporter]

I see what you mean now. I think you've mentioned something like this before, 
no one paid attention. basically this will be "back" button doing something 
like "undo".

Original comment by sv767%ny...@gtempaccount.com on 2 Aug 2010 at 2:01

[GoogleCodeExporter]

Honestly, I believe this behavior is expected and I don't think there is 
anything wrong with it.

Original comment by renc...@gmail.com on 2 Aug 2010 at 2:14

[GoogleCodeExporter]

I agree this isn't a bug by any means and functions as expected, but it does 
warrant consideration for a redesign.  It can take awhile to add all your 
filter/action data, and with one click wipe it all out.  Which can be very off 
putting to new users.  Especially if they aren't familiar with the app.

I just realized if we handled the input as described in Issue 115, this would 
fix this.  I'm going to mark this a dup of that ticket.

Original comment by case.and...@gmail.com on 2 Aug 2010 at 2:22

• Changed state: Duplicate

[GoogleCodeExporter]

Yeah, I don't like the idea of this issue, but I think issue 115 makes a lot of 
sense.

Original comment by renc...@gmail.com on 2 Aug 2010 at 2:30