Howdy Tracy,
Hmmm... Yes, that is an issue. It's fixed in 1.3.7, but apparently not in 1.4.4 yet. The fix will be in 1.4.5, but obviously we don't want to wait for that (if we don't have to). We've just updated the GitHub repository with the fix just now. Could you get the source from there?
m