Cocoa Bindings and CALayer (continued)

Well, I figured out what my problem was. It turns out it was my oversight after all. The problem was that I was keeping track of only 1 bound object at a time. In other words, if Engineering was being trained and the original branch I pulled up contained 2 or more Engineering CALayer before looking at a different branch, my app would only unbind the last Engineering CALayer. Once the new branch gets pulled up its only a matter of time before a Key-Value-Observing notification be sent to an unbound but non-existent object, causing a crash.

Rather than waiting to accomplish a significant amount I'm going to try to submit my code and generate a release very soon as I think this is a pretty critical bug.