|
Size: 550
Comment:
|
Size: 1135
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| == Far future things to address == '''Possible future change of the use of DBindingList''' DBindingList was something I created to deal with being able to delete an item properly when a GUI object like a DataGridView deleted a row and hence a object from a list. The functionality to delete the item is called by DBindingList using an Interface called IDeleteable (also created). It is possible that this could be taken care of in a destructor and still use a straight BindingList<myClass> where myClass has destructors that do what is called using the IDeleteable interface. |
Program Changes Requested/Identified
These are not bugs. Report bugs on the ArchaeologyProgramBugs page.
1/7/2009
- (Todo) The designation in the identification section should be a drop down that equates to what the locus actually "is" See MPP list of types under "Stratigraphy". Dropdown menus in the levels should be taken from "Designation".
- (Todo) The "Location" field in many parts of the Identification section should be a reference to a point taken with the total station. Fix the "text" and check the type.
Far future things to address
Possible future change of the use of DBindingList
DBindingList was something I created to deal with being able to delete an item properly when a GUI object like a DataGridView deleted a row and hence a object from a list. The functionality to delete the item is called by DBindingList using an Interface called IDeleteable (also created). It is possible that this could be taken care of in a destructor and still use a straight BindingList<myClass> where myClass has destructors that do what is called using the IDeleteable interface.