-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Behavior of back button/key #253
Comments
Actually a User has a clue when he is on a Home screen: no Up button on an Action bar. |
BTW, Back and Up buttons are not the same... |
Agree, back button should go back from current view state to previous view state. If I change the view state and back button closes the app, that's confusing -- especially when in a "custom" mode like search. I have closed AndStatus many times due to this. |
@clacke I recently thought about allowing the Timeline Activity to have multiple instances. The main problem, which we may face in that case, will be "Out of memory" error. |
I think that we don't need multiple instances of a Timeline. We could just remember a history of timeline switching. And go back that history (switching in reverse direction...) |
I just posted #356 which is pretty much the same issue. Is it not possible to have a "home/back-option with the home setting being the default TL position? |
referred of #422 Yes, I think we mean the same. I summarize again: This symbol is above if I am the start time line on. on the left: I have this back arrow at many but not all undersides: It would simplify the navigation very much if this arrow on every underside existed. |
@b2410 What you show on your screenshots is "Up" button, which is about navigation in a hierarchy of views (e.g. navigation from a Conversation view to a Timeline). Please read this carefully: https://developer.android.com/design/patterns/navigation.html (I did this right now...) Taking that Android guidelines and terminology into account I think that "Up" button, which you showed above, works correctly (at least in most cases...). |
…avigation, in reverse chronological order, through the history of screens the user has recently worked with. See https://developer.android.com/design/patterns/navigation.html Return to the Default timeline clears the whole history stack, so when a User presses "Back" button on the Default timeline, he/she leaves AndStatus (and returns usually to the Home screen of the Device).
Excuses my mistake. I have never noticed the difference. It is working now as described in the link. But on the user timeline is the problem that the "up" button not exit and the "back" button close andstatus. |
Implemented in v.30.00. Please test: the Open Beta testing channel https://play.google.com/apps/testing/org.andstatus.app |
@yvolk It functions perfectly. Thank you. |
@b2410 Actually the change was trivial. Why I didn't do this earlier: I was afraid that this would cause out of memory issues. Please report if you have them after this change. |
@yvolk I test it 5 days without problems. The app or the phone was not restarted. More Ram is not required. |
@b2410 Thank you for the feedback! |
When I search for something and I want to go back to main timeline the back button/key closes AndStatus despite going back as expected. Same thing for going back from Mentions to main timeline.
I think that's no big problem but a bit confusing compared to other (social networking) apps.
The text was updated successfully, but these errors were encountered: