Hi,
we still have this problem in 7.1.5.1396.
Any chance to fix it with the next version?
Thanks Frank