Well, specifically I don't know if this is an issue with Core Animation layers or I'm doing something stupid. What I'm doing is programmatically binding a CALayer to a managed object with a particular key path. The problem occurs when I destroy that layer. It causes the program to crash. This is due to the a value of the object being updated (incremented skill points) and as a result it sends KVO messages to all listening objects. The CALayer never got unbound and thus a message is sent to a deleted object.
Well, I figured the simple fix is an unbind: call. At least I thought it was. The app still crashes.
I'm not sure what I'm going to do. My first guess will be to apply bindings via a NSObjectController I programatically create.
In any case, I'll hopefully finish the skill browser this weekend and start focusing work on the skill plan next week.
Posts
No comments:
Post a Comment