@tadano That was fixed in 3.3.0, could you confirm (in the issue thread)?