Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS7 custom interactive transition, hidden back button reappears as "..." when cancelled
    primarykey
    data
    text
    <p>I have a custom interactive transition which requires me to hide the standard back button. Basically, the transition looks like a push from left-to-right rather than the standard right-to-left push we're all familiar with. That's why my back button is on the right side instead.</p> <p>As you can see from two screenshots I took before and after cancelling pop transition activated by a UIScreenEdgePanGestureRecognizer, once the transition is cancelled there is a "..." where the back button would be. </p> <p><img src="https://i.stack.imgur.com/q7TFK.jpg" alt="Before and After Cancelling the transition"></p> <p>I'm currently using </p> <pre><code>self.navigationItem.hidesBackButton = YES; </code></pre> <p>and I've tried putting it in <strong>awakeFromNib</strong>, <strong>viewDidLoad</strong>, <strong>viewDidAppear</strong>, <strong>viewWillAppear</strong> methods all without fixing the problem.</p> <p>So using the power of Reveal.app I investigated the view hierarchy before and after and saw this:</p> <p><img src="https://i.stack.imgur.com/Npebx.jpg" alt="View hierarchy before and after via reveal.app"></p> <p>What you see highlighted in each part of the image is what appears to be changing in the area of the nav bar that contains the hidden back button. Before it's a UINavigationButton and then it becomes a UINavigationButtonItem with a UILabel, which must be what contains the "..." and remains like this.</p> <p>Any help would be much appreciated. I hope this is detailed enough to give a good picture of the issue.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload