-
Notifications
You must be signed in to change notification settings - Fork 676
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
Problem with back button not working #1
Comments
The category inserts an overlay view to the navigationBar to achieve the effect. Once you call |
Leo: Thanks for getting back to me and I appreciate your writing the code. I would like the user to be able to use the back button while keeping the clear effect on, but that may not be possible. I’ll check it out some more and see if I can make it work. Cheers, Peter On Feb 26, 2015, at 9:37 PM, Leo <notifications@github.commailto:notifications@github.com> wrote: The category inserts an overlay view to the navigationBar to achieve the effect. Once you call [self.navigationController.navigationBar reset];, the overlay view will be removed, everything should be back to normal. If you still have the problem, you can send me your code. — |
Please see my Pull request #2 with the solution for given issue. |
Wow, that is an elegant fix! I added my own code to position a clear button where the back button was and then got the navigation controller to pop the view. I will put your new code in and see how that works. Thank you for working on this. Cheers, Peter On Mar 5, 2015, at 2:52 PM, xZenon <notifications@github.commailto:notifications@github.com> wrote: Please see my Pull request #2#2 with the solution for given issue. — |
Thanks for the fix @xzenon |
I just tried your fix and it works great! Thanks. -Peter On Mar 5, 2015, at 2:52 PM, xZenon <notifications@github.commailto:notifications@github.com> wrote: Please see my Pull request #2#2 with the solution for given issue. — |
Awesome code for a nice effect, thank you. I have one problem where the back button does not work any longer when I navigate down a few layers. Any idea what that could be? It might be my code.
The text was updated successfully, but these errors were encountered: