When in the dialog for editing the track tag, pressing the Android back button does not return to the last menu (exit the edit tag dialog). I believe this is the only menu that does this, so I don't know if this is an oversight or intentional. My feeling is that pressing back should always back you out of whatever you are in without changing any potentially changed info. Thus, my feeling is back should be the same as cancel. This is probably as intended and just not functioning.
MMA 146 (currently due to sync issues but experienced in basically all versions)
Droid4 ICS 4.0.4
[BUG] Back button doesn't work
Moderator: Gurus
-
- Posts: 193
- Joined: Mon Jan 02, 2012 10:42 pm
Re: [BUG] Back button doesn't work
While that's generally true in the Windows world, I think it's actually the opposite in Android. I'm pretty sure Android's standard is to use Back as "Save and Exit". For example, think about when you go into the Settings or Preferences screens in most apps. Don't you find that there usually is no Ok button and you just hit Back to commit your changes?bkenobi69 wrote:My feeling is that pressing back should always back you out of whatever you are in without changing any potentially changed info. Thus, my feeling is back should be the same as cancel.
Remember when Last.fm had those cool imagegen charts for use in signatures?
Re: [BUG] Back button doesn't work
I would say that in general there are no 'ok' or 'cancel' buttons in most android apps. In such a case, I would assume changes are immediately committed without any available undo. If a menu has 'ok' and 'cancel' buttons, I believe in all situations a back button (be that clicking 'cancel', hitting the escape key, clicking the 'x' in the corner, or whatever) should always back out without committing changes.
-
- Posts: 193
- Joined: Mon Jan 02, 2012 10:42 pm
Re: [BUG] Back button doesn't work
Whether or not there are Ok/Cancel buttons is an interesting distinction that I wasn't considering. My immediate reaction is the Back button is then ambiguous in that context, so maybe disabling it is better.
In fact, funny this should come up right now, because I just got tripped up by this exact thing in gReader. In the feed preferences screen there are Ok/Cancel buttons, and on that screen the Back button is implemented as you suggest. I was so set in the habit from other apps of just making a change and then hitting Back that I didn't even notice the Ok/Cancel buttons at the bottom. I had like 15 feeds that I wanted to change something about, and I didn't realize until about the 12th one that I had been cancelling the changes each time. I had to start all over.
But maybe that's just me being stupid. If it is standard in Android that Back = Cancel when Ok/Cancel buttons are present, then I'm all for MMA following that. I guess I'll have to keep an eye out for this in more apps to see what's typical before I can really say whether I agree with you here or not.
In fact, funny this should come up right now, because I just got tripped up by this exact thing in gReader. In the feed preferences screen there are Ok/Cancel buttons, and on that screen the Back button is implemented as you suggest. I was so set in the habit from other apps of just making a change and then hitting Back that I didn't even notice the Ok/Cancel buttons at the bottom. I had like 15 feeds that I wanted to change something about, and I didn't realize until about the 12th one that I had been cancelling the changes each time. I had to start all over.
But maybe that's just me being stupid. If it is standard in Android that Back = Cancel when Ok/Cancel buttons are present, then I'm all for MMA following that. I guess I'll have to keep an eye out for this in more apps to see what's typical before I can really say whether I agree with you here or not.
Remember when Last.fm had those cool imagegen charts for use in signatures?
Re: [BUG] Back button doesn't work
I've only been using Android for around a year and I have not reviewed any OS design documentation. I can't say I know what is standard according to Google nor the industry. What I can say is that most applications do not have a set of OK/cancel buttons. In that case, changes are immediately committed. I'm OK with whichever approach MMA goes with, I guess I was just pointing out that the back button does not work in that location. If that's by design, cool!