@SimonWoods Sorry, I can see how that might happen actually. Does it fix itself if you just quit and open the app again? I'll probably do another release tomorrow with some additional checks for this situation.