Thank you for your report. The fix implemented in 0.3.5 may have caused a new issue. I have already updated the revised version. The version number remains 0.3.5.
