The problem has been identified and solved! (a check was needed to see if the textbox was writable before updating the value).
Thanks for your bug report, you can download the latest update, 1.0.9 which corrects it
