Glad to hear the first issue was fixed!
You never miss a trick @Wolfgang!
This should now be fixed in 1.3.0.1. I would appreciate if you could let me know if this is the case on your end.
Thank you!