This file forces the program to open the recently created file after all RFIDs have been mapped. This fixes issue #233.
Fixes #233
What was changed?
map_rfid.py was changed to allow to go straight from experiment creation, to rfid mapping, to data collection, without having to open or close any files.
Why was it changed?
The issue was that if a new experiment was created, the user would have to reopen it after mapping rfids but before being able to utilize the data collection page.
How was it changed?
map_rfid.py now stores relevant information locally, such as the parent experiment menu frame and the local path where the newly created experiment is stored. From there, when the user hits the back to menu button, assuming all rfids have been successfully mapped, it then closes and reopens the file back to the experiment menu page. From there, the user can directly navigate to the data collection page without issue.
Screenshots that show the changes (if applicable):
This file forces the program to open the recently created file after all RFIDs have been mapped. This fixes issue #233.
Fixes #233
What was changed?
map_rfid.py was changed to allow to go straight from experiment creation, to rfid mapping, to data collection, without having to open or close any files.
Why was it changed?
The issue was that if a new experiment was created, the user would have to reopen it after mapping rfids but before being able to utilize the data collection page.
How was it changed?
map_rfid.py now stores relevant information locally, such as the parent experiment menu frame and the local path where the newly created experiment is stored. From there, when the user hits the back to menu button, assuming all rfids have been successfully mapped, it then closes and reopens the file back to the experiment menu page. From there, the user can directly navigate to the data collection page without issue.
Screenshots that show the changes (if applicable):