Just to show I haven't forgotten about this, I can confirm that the problem still exists in v1.1.25 :-(
Just to show I haven't forgotten about this, I can confirm that the problem still exists in v1.1.25 :-(