-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decide on signal bars #860
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
My opinions on this:
The only way to avoid the inconsistency seems to be to not use the information we have for non LE devices. The signal bars are probably not that useful to most users, but I'd not downgrade that UI for consistency reasons. |
I'm leaning towards using using a Gtk.LevelBar as seen in #1768. But this requires quite a bit of work replacing the TreeView. |
With bluetooth LE we do not have signal bars. The problem afaics is that we do not have tpl, lq and rss. We do have an rssi property in the dbus api but it is only available during discovery.
While it has been a big part of blueman the simplest would be drop them and instead have an indicator showing if the device is connected. I can add the indicator on top of the bars as well but this will make the ui inconsistent between LE and non LE devices.
Opinions, suggestions, complaints :-)
The text was updated successfully, but these errors were encountered: