Hi again elacris I just wanted to let you know that we have put a fix into 1.2.0b that should fix the issue that you experienced. :)