That bug should have been fixed a while ago. Can you please verify you are using the latest version (3.2.0) and try again?
I downloaded 3.2 and indeed fixed this issue. Thank you very much
Awesome!
