Yes, Steve has been great and has already fixed the problem in a beta I tested. I believe he will be releasing it very soon.

Thank you for reminding me about versions affected. Steve indicated to me that the bug was introduced in V4.1.0.62, and I am running V4.1.0.60 currently which works fine.