Will this be fixed in a future v.1.6.x release, or perhaps v2?

Reply via email to