Great you found a fix.
But with duration of 0.0, what is the interest of running animation ?
You should get the same result by calling directly setBoundsOrigin(NSMakePoint(0, scrollView.contentView.bounds.origin.y))
I was also wondering what do you expect by animating the bounds origin ?
I remember I once had problems to stop Animations with removeAllAnimations.
The case:
animating a window resize by setting its frame.
the button (inside the view that was animated) that was supposed to stop it did react (highlighted) but did not execute apparently.
I found out that it was as if the animator created a new view and was performing animation on it ; hence the removeAllAnimations was not sent to the right one.
But if animation was to set alpha of a label, it could be interrupted by the button action (button was not included in the animation).
Maybe (I'm not sure) animating the bounds create a similar issue.
Topic:
UI Frameworks
SubTopic:
AppKit
Tags: