On 26.11.2015 18:13, Markus Alexander Kuppe wrote: > the newest nightly build [1] does not show this problem anymore. I did some quick tests and I can confirm that the nightly dated 26-Nov-2015 16:29 does not have this problem. Thanks! :) Jaak