I didn't check before I posted this note. I upgraded to 1.2.0 and the behavior seems to have stopped for now. This isn't the first time I've experienced this behavior though. In the past an update has fixed it, other times I've been up to date and had to reinstall (I just reinstalled both applications for posterity) and that has worked.