-
Notifications
You must be signed in to change notification settings - Fork 168
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
"Show next break time in tray icon" isn't working #643
Comments
I believe B was caused by #558 |
The current code tries to put the time in a tooltip, but that's not really right. We don't want to have to hover to see the time. Anyway tooltips seem to be unsupported in AppIndicator. The previous code used However StatusNotifierItem seems to be missing a function for label. |
Please can the main contributors for the issue that caused this regression join the discussion here? |
…ay icon" Fixes slgobinath#643 this a non-standard attribute that is not supported by many desktops, e.g. KDE and snixembed however, this also did not work with libappindicator on KDE before
Regarding C - at least on KDE Plasma, there's a method to integrating xdg-activation into the tray icon ("ProvideXdgActivationToken"). Looking at this, it seems the GNOME extension supports it too. |
Great thanks. I confirm that the PR works on Gnome. |
I raised #649 |
Sorry about my silence in the past several weeks. I can test the PRs tonight. |
@archisman-panigrahi #646 is probably the highest priority. |
Great thanks for the fix.
|
Describe the bug
After a recent upgrade, the setting "Show next break time in tray icon" isn't working
To Reproduce
Click on settings, select plugins, open Tray Icon settings and enable "Show next break time in tray icon". Nothing happens, I don't see the time.
Expected behavior
I see the time adjacent to the tray icon.
Desktop (please complete the following information):
Debug Log
Run the Safe Eyes using
safeeyes --debug
command attach the ~/safeeyes.log` file.Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: