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.

Skill Browser...

...is 85% complete! Everything aligns properly. The data, from what I've tested, is accurate. The colors... need work. I may not have the fancy gradients that EVEMon has but I'm happy with solid colors. The solid red and blue colors kind of make it difficult to view the text. I'll try to get that fixed next time I submit. My only other complaint is that when the skill planner window initially loads, the branch view is scrolled to the bottom left corner rather than starting at the top left. I've tried a few things to set it to start at the top including doing it programatically but in doing so, such attempts produced problems of their own. 

A few things from the Core Data model have changed so it would be advised to delete the old store. Maybe later on I'll automate the process. Although, in doing so, I'll have to create a mapping model. Never had good luck with those. Also, I changed the store over to a binary format. You'll notice that storing and loading is now more than twice as fast.

I've posted build 38 in my google site link. If you've encountered any bugs while using the skill browser window, let me know.

Core Animation!

Yes, I'm aware that this app doesn't have a real need for animation nor do intend to utilize any. Core Animation does have two great advantages for me: it's fast and it's easy (relatively speaking). It's been about a year since I even looked at CA so I spent much of my day doing some catching up on the basics.

The screenshot posted is more or less a skeleton of where I am now. I do plan on doing left to right tree growth. The size, color and content of the boxes will all definitely change but, after hours of fidgeting around with math, the box positioning looks right. I'm still trying to figure out how CATransform3DRotate works and getting the connecting lines' angles right. One big concern, though, is the size of the view. Currently, its static (and too big, for that matter). Ideally, it should be adjusted to the size of the tree to eliminate unnecessary scroll bars if the tree fits inside the view.