Forums
(@timsondermann)
6 years, 2 months ago
As predicted, the problem is gone with v6.5.0. Thanks for the constructive input, gentlemen.