A new Events class has been introduced to handle event detection on a separate thread, allowing the Director class to focus on directing the flow of traffic, so to speak, rather than also being responsible for event detection. Along with this came a number of additions and movements to the common file, as well as changes to the settings file. The Events class now creates and updates the drivers list (which is now stored in common), detects events, and puts those events into a queue with all of the information needed to generate commentary. In the future, this queue can also be filtered by event type and time, to allow for prioritization of specific events.
Fixes #46
Type of change
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
Testing
Numerous tests were run throughout the process of creating the Events class and refactoring other code, ensuring that the functionality of the software is unchanged on the surface.
Description
A new Events class has been introduced to handle event detection on a separate thread, allowing the Director class to focus on directing the flow of traffic, so to speak, rather than also being responsible for event detection. Along with this came a number of additions and movements to the common file, as well as changes to the settings file. The Events class now creates and updates the drivers list (which is now stored in common), detects events, and puts those events into a queue with all of the information needed to generate commentary. In the future, this queue can also be filtered by event type and time, to allow for prioritization of specific events.
Fixes #46
Type of change
Testing
Numerous tests were run throughout the process of creating the Events class and refactoring other code, ensuring that the functionality of the software is unchanged on the surface.