title: What exactly does removedOnCompletion = NO do?
body: <p>CAAnimation provides the removedOnCompletion property which defaults to YES.</p>
  
  <p>Let's recognize these facts:</p>
  
  <p>A) Core Animation only affects the Presentation Tree, but not the Model Tree. When an animation is done, you end up seeing whatever is set in the Model Tree. You can set a fillMode to kCAFillModeBoth for example, which will swap the value from the Presentation Tree over to the Model Tree once the animation is done. This causes your animation to not revert back (which is most likely what you want).</p>
  
  <p>B) I did an experiment. removedOnCompletion = NO will <em>NOT</em> have the same effect as kCAFillModeBoth or kCAFillModeForwards. To be more precise: It has absolutely no effect on how the result looks like when the animation is done. Wether it is "removed" or not, it seems to not affect the Presentation Tree at all.</p>
  
  <p>To explain what removedOnCompletion really does, the documentation is too weak in this regard. I don't get it. Can anyone explain what exactly would be removed, and what's the benefit of not having it removed?</p>
  
  <p>My guess is that Apple is talking about the animator object itself, which is added to the layer with -addAnimation:forKey: ... but again: What's the point of keeping it around?</p>