We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Nothing happens (also no back indicator displayed)
Go back one level
2016.03.29-NB
Yes
Probably not a new bug
The text was updated successfully, but these errors were encountered:
I confirm, this isn't a new bug.
However, I've used c:geo for the first time on a tablet this week-end. Our design is not tablet friendly at all. I would love to see that change. We could use v7 Preference Support Library (Gradle: com.android.support:preference-v7:23.2.1) (I think this would need upgrading to com.android.support:appcompat-v7:23.2.1 #4903). Then we could display nice settings UI like http://developer.android.com/images/ui/settings/settings-headers-tablet.png / http://developer.android.com/images/ui/settings/settings-headers-handset.png
v7 Preference Support Library
com.android.support:preference-v7:23.2.1
com.android.support:appcompat-v7:23.2.1
More generally, migrating technically to Fragments could help us going to a new design... ie #5111
Fragments
See also: http://developer.android.com/tools/support-library/features.html http://developer.android.com/guide/topics/ui/settings.html
This would need to be discussed on another use (I'll open it later)
I propose not to pass much time here (unless a quick fix is available...)
Sorry, something went wrong.
moving-bits
Successfully merging a pull request may close this issue.
Detailed steps causing the problem:
Actual behavior after performing these steps:
Nothing happens (also no back indicator displayed)
Expected behavior after performing these steps:
Go back one level
Version of c:geo used:
2016.03.29-NB
Is the problem reproducible for you?
Yes
Other comments and remarks:
Probably not a new bug
The text was updated successfully, but these errors were encountered: