Confusing behavior if no collection is installed

The 0.2 newAPI daemon does not crash anymore in such case. However, the viewer might indeed display a warning in this case.

I have added a message to resolve this bug, but I want to have a more elegant solution in which you can click a scan button to have the daemon rescan the collection. The challenge is that I don't think we currently have a means to do this - I could run _load_accomplishments() but if the daemon is not restarted, it doesn't do a rescan of the accomplishments collections.

Calling API's reload_accom_database() should do the trick. It should rescan all directories for accomplishments and load a new database.

Alright, I implemented this. Clicking "Scan again" on the message will reload accomplishment collections, same for a new Edit menu item "Reload accomplishment collections" <- that's the one that may be useful for accomplishment contributors, they won't need to restart the daemon anymore :-) Also, there is a statusbar message when reloading takes place, either to inform the user that the daemon is rescanning collections, or to ask him to wait a second.