As an end-user, I want to choose which functions to display in the application UI at a time, so that I can separate conflicting functionality.
Acceptance criteria / bug explanation
The layout should be able to switch content without the Bluetooth and WiFi hardware connections.
The switch content button only displays and hides content on the screen, so it should be functional even when hardware is disconnected. Rather, it's the content being displayed that should not be clickable until connection.
This will be fixed by making the switch content button clickable again, despite disconnect, but also include a toast notification when the user tries to click the nav buttons without connecting to hardware in a later step after the switch content.
User story
As an end-user, I want to choose which functions to display in the application UI at a time, so that I can separate conflicting functionality.
Acceptance criteria / bug explanation
The layout should be able to switch content without the Bluetooth and WiFi hardware connections. The switch content button only displays and hides content on the screen, so it should be functional even when hardware is disconnected. Rather, it's the content being displayed that should not be clickable until connection.
This will be fixed by making the switch content button clickable again, despite disconnect, but also include a toast notification when the user tries to click the nav buttons without connecting to hardware in a later step after the switch content.