20 Feb
2001
20 Feb
'01
2:55 p.m.
It is already fixed in 2.3 from public CVS.
But, ominously, not in the 2.3.1b1 release ;-)
Probably because the fix was checked in *after* the 2.3.1b1 release. Steve was pointing out tthat the fix is on the 2.3 branch, which means it will be in the next 2.3 series release (likely to be 2.3.1).
Looks like someone fixed this in the trunk but forgot to merge the fix to the release branch :( It's fixed for 2.3.1 final. Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com