@hnla
13 years, 6 months ago
I really hope you’re wrong about that as this ongoing issue was meant to have been corrected once and for all in 1.2.6.
