Known Problems with the Chronicle Plugin

  1. I get the Error: "Can't set «Class imaA» of "" to «Class imaA» id 2."
  2. Other 3rd-party Xcode plugins I have installed quit working when I installed Chronicle Plugin
  3. Chronicle inserts text into (or captures text from) the wrong Xcode text document

This error is caused by a cocoa incompatibility with the plugin architecture, and occurs when the plugin is loaded while Xcode is launching. This issue has been resolved as of version 0.9.3 of the plugin. Users experiencing this problem or using version 0.9.2 of the plugin should update to the latest version, by visiting the Chronicle Home Page and following the latest Download link.

See also:
Chronicle Home Page

This still-unresolved problem I believe is related to how Xcode builds it's menu items at launch-time. When more than one 3rd-party plugin that build a custom main menu item is installed, only one of them succeeds in loading. The remaining plugins fail to load, and a variety of errors will be posted, depending on the setup of each plugin. I have not been able to find any solution for this problem, and will do my best to resolve this problem in a future release. If anyone has encountered this behavior... or better yet, if you have RESOLVED this problem... please contact the author with any information or resources you can offer.

Xcode's internal list of active text documents is a linear array of file references. The list does not reflect the front-to-back ordering of the documents, but instead is merely a record of the order in which text documents are opened and viewed during each project session. Previous versions of the Chronicle Plugin attempted to reference the active text document by using 'text document 1', similar to how one might reference the application's active windows. Further testing illustrates that this reference will always refer to the first document opened during the session, and does not refer to the frontmost document.

This issue has hopefully been resolved as of version 0.9.5. Users experiencing this problem or using version 0.9.4 or older of the plugin should update to the latest version, by visiting the Chronicle Home Page and following the latest Download link.