Comment by bproven

thanks!

Looks like the first and last issue is fixed in 1.0.0 (released 2 days ago). So only that second issue remains for now.