Comments
-
Greg Hurrell
I suspect that this is probably a duplicate of an existing ticket, most likely ticket #640, but I'll need more information. If you're using the 3.5 series and Leopard then that is almost certainly the case. Please see that ticket for full details (the short version is that this is an Apple bug and I'm waiting for a fix from them, but in the meantime the 3.2 series works fine on Leopard and is feature-equivalent).
-
anonymous
Yep, Leopard and v3.5a5. I'll follow #640 from herein and revert to 3.2. Thanks!
Add a comment
Comments are now closed for this issue.