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.

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

Swipe back from crag causes that crag to dissappear from the map #64

Closed
DaneEvans opened this issue Mar 13, 2021 · 5 comments
Closed

Swipe back from crag causes that crag to dissappear from the map #64

DaneEvans opened this issue Mar 13, 2021 · 5 comments

Comments

@DaneEvans
Copy link

If you swipe left one too many times, you end up back at the map - annoying, but fine.

Only the crag that you were just in isn't there anymore...

You have to reboot the app due to a misclick, Another option is to click on a different random crag, then go back again, so that the one that has dissappeared is the one that you never cared about

@bkucsera
Copy link

This happens when there is no selected crag, it happens usually after a new app start.
If there is a selected crag from the map, and you go back from a crag to the map with the back button, you will end up on the map on the selected crag.

So if you have not chosen any crag on the map, just started browsing the crag list menu and you go back to the map, you would like to see that area/region/country, what you browsed in the list view?

@DaneEvans
Copy link
Author

DaneEvans commented Mar 17, 2021 via email

@rouletout
Copy link

@DaneEvans I'm not sure I get it, if I swipe left I'm unable to end up on the map, only on the Index page. Can you check again and maybe supply a screenshot from where this happens? Thx

@DaneEvans
Copy link
Author

DaneEvans commented Mar 22, 2021 via email

@rouletout
Copy link

ok, clsoing this as it seems solved - please re-open if you see that again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants