4 ms·
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 i
by chris_7 10y ago
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.
- interpol_p 10y agoThose 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.
- richardwhiuk 10y agoThat'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].
- interpol_p 10y agoYes, I am saying that it's a horrible fix and you shouldn't do it. Sorry I didn't make that clear.