Making changes to cage_config_ui, data_collection_ui, experiment_menu_ui, map_rfid_ui, new_experiment_ui, select_experiment_ui, and tk_model ui
The changes to cage_config_ui, data_collection_ui,, and map_rfid_ui was made to allow them to disconnect from database. The changes were made to allow the database file to be removed properly when user decides to delete the experiment.
The implementation of delete button function was in the experiment_menu_ui, where the function to delete the db file, csv data, and backing to the selection_ui. To allow the label to be updated in the selection_ui once the experiment was deleted, a new abstract class was added to the tk_models file and inherited by the select_experiment_ui. After the implementation, I also added a check to the experiment naming convention in new_experiment_ui so that it checks if an experiment with the same name already exists, and if it exist, raise a warning.
Connecting the delete button to the Experiment menu gui, as well as implementing the functionality of deleting the corresponding db file, removing the experiemnt information on the csv file, and returning to the selection gui. The corresponding experiment's label is also updated and removed on the selection gui.
Fixes the issue that allow the user to create experiments with name used by previous experiments by implementing check once user uses a name taken by previous experiments and raising warning.
Fixes #70
Making changes to cage_config_ui, data_collection_ui, experiment_menu_ui, map_rfid_ui, new_experiment_ui, select_experiment_ui, and tk_model ui
The changes to cage_config_ui, data_collection_ui,, and map_rfid_ui was made to allow them to disconnect from database. The changes were made to allow the database file to be removed properly when user decides to delete the experiment. The implementation of delete button function was in the experiment_menu_ui, where the function to delete the db file, csv data, and backing to the selection_ui. To allow the label to be updated in the selection_ui once the experiment was deleted, a new abstract class was added to the tk_models file and inherited by the select_experiment_ui. After the implementation, I also added a check to the experiment naming convention in new_experiment_ui so that it checks if an experiment with the same name already exists, and if it exist, raise a warning.
Connecting the delete button to the Experiment menu gui, as well as implementing the functionality of deleting the corresponding db file, removing the experiemnt information on the csv file, and returning to the selection gui. The corresponding experiment's label is also updated and removed on the selection gui.
Fixes the issue that allow the user to create experiments with name used by previous experiments by implementing check once user uses a name taken by previous experiments and raising warning.