Closed Iyury1 closed 1 year ago
Here's the PR resolving this issue. #18. Other than the TelemetryModel itself, many more changes were made in how sockets and GUI are connected. The PR lists all of them. A few more changes are required. Don't merge the PR before they are made. (Check #18 )
Summary
Use the example from Issue #13 https://github.com/albertaloop/T_SWE_2022_2023/tree/GUI/qt-modelview/GUI/TableView-example
We need to create a class called "TelemetryModel" as indicated in the UML Class diagram
The "TelemetryModel" will inherit from QAbstractTableModel and will provide data to a TableView class belonging to the "MWindowWrapper" class. The TableView example above demonstrates how to do this. "MWindowWrapper" is defined in "main2.py", and inherits from the "Ui_MainWindow" class defined in "AlbertaLoop_UI2.py".
"TelemetryModel" will contain a list of Telemetry data that will be received as telemetry packets from the "TelemetryReceiver" class. The format for the packet including the types of data are listed in a table in the Network Comms design plan located on our Google Drive: Albertaloop 2\3 - Electrical\2 - Software Group\1 - Design\T_SWE_PLAN - Network Communications.gdoc
Acceptance Criteria