It turns out BTW this is in part a bug, fixed in 5, but I don't know if it's a bug in the "it doesn't work" sense or just the "you see that warning" sense. Either way, it was fixed and I'll quickly backport the fix in case there's ever a 4.x patch. -- Scott