@drwebbe
2 years, 5 months ago
I created a ticket in the bugtracker
The error still exists in v10.3.0
