News for hackers. Stuff that matters.
Re:React Native Navigation Library by chris_7 on Tuesday March 14, 2017 @01:38AM (#13865279)
I've definitely seen an animation issue where the typical _async -> main didn't work, but _after (0.001 seconds or so) on main did. Though I don't remember if it was on Mac or on iOS, or really what the issue was.
Re:React Native Navigation Library by interpol_p on Tuesday March 14, 2017 @02:10AM (#13865410)
Those animation issues pop up often, and you can get around them by using DispatchQueue.main.asyncAfter(.now() + 0.1) but often you can figure out what the actual issue is (i.e., you're likely attempting to present something in the wrong place) and you should do that instead.
Re:React Native Navigation Library by richardwhiuk on Tuesday March 14, 2017 @07:02AM (#13866472)
That's a horrible fix, introduces jank, and doesn't work cross device.

You normally want a CoreAnimation completion block ([CATransaction setCompletionBlock:^(){}], with an enclosing [CATransaction begin] and [CATransaction end].

Re:React Native Navigation Library by interpol_p on Wednesday March 15, 2017 @07:08AM (#13875254)
Yes, I am saying that it's a horrible fix and you shouldn't do it. Sorry I didn't make that clear.