Closed bshepherdson closed 8 years ago
I thought that the ObjectReplicator was not used in the DAOCreateController.
The ObjectReplicator listener should probably be merged to 100ms or so, such that rapid object changes don't hammer the DAO.
But even if that fixes the problem, that feels like a hackish fix. Something not dependant upon timeouts would be more robust.
Observe that the new row in the list is blank, and then fills in. If your DAO persists, and you reload, you'll see that the value was never set in the persistent DAO.
Probably this can be solved by delaying the
ObjectReplicator
callingput()
slightly.