Fixed in v1.5.2, available from the link above (even if it still says 1.5.1 as you're reading this).
A helpful tip: This would have been fixed in 5 minutes instead of 7 hours if I had gotten e-mail telling me about it; it's only insomnia that got me to see it this soon. I don't think I'm atypical of developers in not spending significant time looking over web sites for bug reports. There's just too much content on all the sites, forums and Usenet groups to cull out the high-priority stuff. So whether it's a single programmer or an organization the size of Apple or Microsoft, direct reports are almost guaranteed to get a more timely response.
Pips - Greg_Weston_572
Fixed in v1.5.2, available from the link above (even if it still says 1.5.1 as you're reading this).A helpful tip: This would have been fixed in 5 minutes instead of 7 hours if I had gotten e-mail telling me about it; it's only insomnia that got me to see it this soon. I don't think I'm atypical of developers in not spending significant time looking over web sites for bug reports. There's just too much content on all the sites, forums and Usenet groups to cull out the high-priority stuff. So whether it's a single programmer or an organization the size of Apple or Microsoft, direct reports are almost guaranteed to get a more timely response.
Reply to This
Monday, March 10 2008 @ 01:53 AM PDT