Bug with record field initialisation
There is an initialisation error with record in that the introspect method is not called if you make a new instance with the new language keyword. Basicaly, its all b0rked if you dont use createRecord
Leave a comment
so this doesn't work in 2.8, because the order of initialization has changed. in 2.8, the object singletons for the subclass (e.g. Author) are not yet initialized and so return "null" at the time the superclass (Record) constructor is run. this means that none of the names ever get initialized.
I think we will have to reverse part of this change, and move the introspection back to createRecord. I'll bring it up on the ML, but I can't make screen support work on record as-is in 2.8, since screen wants field.name to be initialized.
I think we will have to reverse part of this change, and move the introspection back to createRecord. I'll bring it up on the ML, but I can't make screen support work on record as-is in 2.8, since screen wants field.name to be initialized.