-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
NavigationController back button moves on each display of a view instance #650
Comments
Can you send a sample project of this? :) Thank you! |
Here you go, just run |
Yes, thank you :) I will fix this for the next release. |
Looking into this today. Thank you! |
Hey, sorry this has not been fixed yet. Let me take a look :) |
I'm seeing this exact same issue in 2.12.16. Is this supposed to be fixed Daniel? |
@muzoman it has not been fixed yet. Basically reusing the same view controller and not initializing a new one causes the issue. It is one of the next issues I am going to fix. |
OK, that's great, thank you Daniel. |
@muzoman anytime. My majority of time is working on the education center. So I am splitting support and that for the next little while. Normally, issues are fixed faster. |
@DanielDahan what timescales do you reckon it might me fixed in then? Just pondering whether to re-engineer my App to not cache all it's view controllers... |
@muzoman I'll release this fix by Friday if it is fixable, which it will most likely be :) |
@DanielDahan that is awsome! :-) Will wait, plenty of other things to do! |
sweet :) |
Hi @DanielDahan, Managed to get time to look at this issue yet? Cheers! |
Looking today :) |
Issue has been fixed and will be in the next release. This is the commit 6f9f6ca. Thank you! :) |
With
NavigationController
, when I push/pop the same instance of a given view, the toolbar's back-button moves to the right each time the view is pushed again. Tested with v2.4.6.If I create a new instance of the view every time I push it to the
NavigationController
, this problem does not occur.The text was updated successfully, but these errors were encountered: