Thanks for the feedback! I noticed that problem too early in the development but never found a "good" workaround unfortunately.
