A heads up:

I changed the signature of ValueEvent to take the value as the second argument 
of the constructor rather than the fourth argument. It looks like there were a 
couple of bugs in framework code which seemed to assume it was already the 
second argument…

Harbs

Reply via email to