You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, GNOME Settings suffers from the same problem.
A Bluetooth connection is not a binary state. It can have multiple states, such as:
Not connected
Connecting
Disconnecting
Connected
Connection failed
At the moment, the "off" state can indicate "Not connected" or "Connection failed", while the "on" state can indicate "Connected" or "Connecting".
Instead, the user should be provided with a button at the top of the page whose label changes from "Connect" to "Disconnect" with a useful glyph such as + and X, alongside a "Connection Status" label in the "Status Information" section. The connect / disconnect button should be disabled while connecting or disconnecting.
Pairing status also appears to be absent from the interface.
The text was updated successfully, but these errors were encountered:
There are toasts (mini-notifications) that update thw user on the state of the connection. ie: when a connection fails a notification pops up saying so, with the exact reason why.
I might add a "failed" icon where the spinner is currently but other than that a switch row is best for the UI in my opinion.
Unfortunately, GNOME Settings suffers from the same problem.
A Bluetooth connection is not a binary state. It can have multiple states, such as:
At the moment, the "off" state can indicate "Not connected" or "Connection failed", while the "on" state can indicate "Connected" or "Connecting".
Instead, the user should be provided with a button at the top of the page whose label changes from "Connect" to "Disconnect" with a useful glyph such as + and X, alongside a "Connection Status" label in the "Status Information" section. The connect / disconnect button should be disabled while connecting or disconnecting.
Pairing status also appears to be absent from the interface.
The text was updated successfully, but these errors were encountered: