> This bug (or at least one that looks very much like it) has been fixed > in version 1.3.8 . The release of this version is imminent, so hopefully > you will have a fix very soon. Sander: Was it fixed? // Rickard