View Single Post
This problem has been fixed in OmniPlan 1.6.3.

-Tom