Can't mount drive with spaces in remote path in 1.3.3+MacFuse 2.0.2

Hey, there -- I mount some drives (via SSH) with spaces in the Remote Path, and after the update to 1.3.3/MacFuse 2.0.2 from 1.3.2+MacFuse 1.x, the drive will no longer mount. I get an almost immediate error dialog: "Drive_Name isn't a valid drive". Also after attempting to connect once to a drive with this problem, I can no longer save changes when editing the drive properties in the Drive Manager, the save and connect buttons are disabled.

In troubleshooting, I tried enclosing the whole path in single quotes, also double quotes, escaping the space with a preceding \ and escaping with URL encoding - %20 in place of the space. Only in the last case (URL encoding for the space character) did ExpanDrive attempt to connect, and then fail because the path didn't exist.

Not sure if it's 1.3.3 or MacFuse 2.0.2 that's the cause, but it appears to be a failing upon checking or encoding the remote path prior to actual connection attempt.

I have a temporary workaround - renaming the directory that I am connecting to (specifically /Volumes/iTunes HD/ ) which in this case requires renaming the physical partition mounted on the remote system to a name without spaces, and that connects.

Anyway, hope this information helps. Thanks for a great product.

Jeff