Hey Omega,
Thanks for the info!
We have received two other reports (1|2) in the meantime describing a similar/the same problem, so we were able to reproduce it.
The problem will definitely be fixed in 1.5 stable.
1 Like
Should have been fixed in the latest 1.5 release 
1 Like