I had exactly the same problem with V4.5 on another computer and found that shutting down the program and opening it again was the only way I could get around it. I am now on a different computer, and so far have not had that problem.