What makes you believe this? Is there a list of fixed bugs (aka release notes)? Anyhow, I just checked, and my version (3.1.1), which still shows the bug, claims to be up to date, so ...Geoff Sim wrote:I believe this was fixed in the latest version.