Fixed OnReadField/OnWriteField init bug

I just noticed that the fields for the OnReadField and OnWriteField fields weren't being explicitly initialised to nil in the table constructor. This was causing some weird problems in one of my own projects, where I repeatedly created and destroyed a table component, and the field read handler for a previous table instance was being reused again in a future one.

I've now added an explicit initialization of the fields to nil