Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't stack fragments on the back stack #130

Open
tuxmobil opened this issue Dec 29, 2015 · 5 comments
Open

Don't stack fragments on the back stack #130

tuxmobil opened this issue Dec 29, 2015 · 5 comments

Comments

@tuxmobil
Copy link
Owner

At least for fragments of the same type (lecture details), don't stack them on the back stack if clicked consecutively. If replacing a lecture detail fragment with a different one, also remove it from the back stack.
@johnjohndoe
Copy link
Contributor

Is this specific to tablet layouts?

@tuxmobil
Copy link
Owner Author

yes

@johnjohndoe
Copy link
Contributor

It would be convenient if fragment manager actions are harmonized as in #113 before looking into this. I further plan to extract common routines into a BaseFragment class.

@tuxmobil
Copy link
Owner Author

I'm not a huge fan of building abstraction layers on top of every Android API. At least that's the common basis everyone is used to.

@MichaelRocks MichaelRocks mentioned this issue Feb 13, 2016
Open
@johnjohndoe
Copy link
Contributor

✅ Resolved here: EventFahrplan/EventFahrplan@f9fe5ff

zoff99 pushed a commit to zoff99/CampFahrplan that referenced this issue Apr 9, 2019
@johnjohndoe
Merge pull request tuxmobil#130 from EventFahrplan/housekeeping
6dd440b 
Simplify lecture filtering and counting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@johnjohndoe @tuxmobil