Based on your thought about setFrame: called multiple times, I do have some
interesting news, though not a full resolution: setFrameSize was getting
called repeatedly with the final size during the animation. I put logging
in setFrame{Size,Origin}: in the view whose constraints are altered. Here's
> New questions:
> 1. Is there any point in using addConstraint/removeConstraint in the
> NSAnimationContext grouping? Seems like it can go before beginGrouping.
The important thing is that the frames are set inside the grouping. Updating
constraints should not cause any frames to be set, only
Ugh, forget the youtube video, it gets too resampled. Just download the
file and watch it if yyou want.
https://dl.dropboxusercontent.com/u/16749188/Animation%20jitter.mov
On Mon, Apr 21, 2014 at 6:15 PM, Julian wrote:
> Hi Jakob, thanks for the reply. I stopped checking the list every day.
>
Hi Jakob, thanks for the reply. I stopped checking the list every day.
Going backwards:
It may be an expensive operation to remove, but these macs seem to be able
to handle it. I'm not noticing any problem on my 2.4 ghz Core 2.
> See also the section "Animating Changes Made by Auto Layout" on the
Hi Julian,
The jittering is probably a result of misusing the animator proxy! The animator
proxy is used when you want to directly change properties, for example the
frame of a view, or the alpha value. When you use autolayout, the frame will be
set by the view's layout method, which does not u
I'm animating frame changes from autolayout. Code to trigger the expand is
shown here. I added QuartzCore.framework to my link libraries, and checked
layer backing for the window's view.
-(void) expand {
[NSAnimationContext beginGrouping];
[[NSAnimationContext currentContext] setAllowsImpl
