SDF should not directly modify in-memory "Table" representation of safe.snap
SDF should only modify the in-memory Table representation of the selected burt file by loading the file. Confirm or other updates should not modify this structure. Instead, they should trigger a reload of the burt file.
This will prevent the structure from getting out of sync with the file because of user action in the SDF controls. (can still get out of sync if file is externally modified.)
If user changes the snap file, SDF should eventually detect this, raise a warning on the overview, and prevent Accepts until in memory table is reconciled with the snap file.
Procedure for accepts:
- Lock snap file
- Verify snap file matches table. If not, warn user and abort.
- Write changes to snap file
- read back snap file into table
- unlock snap file
- Add screen for reviewing differences between table and snap file. These differences will only occur if a snap file has been manually changed outside SDF.