Fixes #134 which was also happening on my machine.
When looking into the problem it appeared that the metaDataCache resolved event actually does not happen on initial load - only on subsequent changes to the cache.
This removes the initialLoad logic and triggers a refresh on Load so that the plugin loads immediately upon opening. Caching should still be present due to listening to the metaDataCache event.
Fixes #134 which was also happening on my machine.
When looking into the problem it appeared that the metaDataCache resolved event actually does not happen on initial load - only on subsequent changes to the cache.
This removes the initialLoad logic and triggers a refresh on Load so that the plugin loads immediately upon opening. Caching should still be present due to listening to the metaDataCache event.
Happy to make any required changes.