Thanks for the detailed report.
I am working on how to cache the images. The trouble at the moment is knowing when to use the cache, and when to update. If you change the track properties and then click the artwork node and the cache is used then the artwork page won't display the changes. I am currently working on a system where the images are cached at system startup, and then updated when you change the track properties, so when you click the artwork node the images will already be correct. This will cut down on the load time hugely, but I'm not sure how stable it will be yet.
I don't really understand this error when the node is clicked for a second time. I know it happens sometimes, although I managed to stop it happening on my machine. I still don't actually know what is causing it. It can't seem to navigate to the page that is created. I'll try a time delay and see if it's because the file hasn't been stored fully yet.
This is definitely a work in progress and is FAR from complete. The next version will create a debug log as it's going along so when you get errors you'll be able to email me the file so I can easily see what went wrong!
Thanks again for all your comments and suggestions
