Jay Tuley

So I just received a report that iChatStatus and Music Image cause iEatBrainz to fail at updating the iTunes library. My guess is because they are continuously polling iTunes through AppleScript. I still have yet to experiment with this.

IndyKit is progressing, I’ve written several classes for encryption and signing data, and the unit tests are all working! I thought it was going to be harder than it was, and now I’m writing a subclass to NSButton which is actually harder than I thought, mainly because the apple documentation sucks. I’ve gotten past the parts that were initially hanging me up, mainly that you shouldn’t lock focus on the controlView inside drawRect: inView:, and just assume what needs focus locked, is locked. Who knew?!!

So right now I’m tracking a bug in iEatBrainz in which the library xml file it’s reading and the actually library when talking through applescript aren’t matching, even when the application waits long enough for iTunes to synch out another update. My first guess was that perhaps there is yet another preset location that iTunes checks for music libraries and those effected might have multiple files which iEatBrainz is choosing incorrectly. However from the preliminary emails I’ve received I don’t think this is the case anymore. So it just occurred to me today that if iTunes Music Library.xml was read only the user wouldn’t notice using iTunes, and sure enought I’ve been able to reproduce the bug symptoms making the library file read only. I’m not sure if this is actually the reason for the reported cases but putting in a check will at least help narrow it out as a cause.

The problem right now is that adding the check will require a new version of IndyKit. IndyKit is a little up in the air right now with other features that I’ve been working on. These features will effect both iEatBrainz and NicePlayer so that release won’t be right away. I’m rather excited though with IndyKit as I believe the classes I’m writing will be very useful to many applications. Once I finish with these classes I will be writing up actually documentation for IndyKit, and officially releasing it.