-
Notifications
You must be signed in to change notification settings - Fork 21
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
Set/persist icon color? #24
Comments
This would be nice |
@ttntm @julianfairfax You can try the new version published last week-end. It includes some new features and I think that what you expect is in. |
It doesn't seem to persist the icon colour though. Maybe I'm using it wrong? |
Same here unfortunately, defaults to blue and does not persist any other selection across sessions. |
the icon color selection is persistent now |
I don't know what changed (or when), but one of the more recent Fedora NB: I did not update onedrive_tray since June 9th. Unless there's any more info you need, I suppose we can close this issue. |
I've installed here from Github a few days ago. Every start the icon is blue, changes are not persistent. Btw works not under Wayland for me. |
Same for me, the icon starts with blue and is not persistent after restart. (on Ubuntu 22.04/Gnome) |
I don't understand. My distro is Ubuntu 22.04.1 LTS / GNOME 42.2 and it works perfectly. |
Can you give details about your distro ? |
@Morikko @tmode-1960 |
Yes, quitting the application by the menu saves the color icon. Previously, I was doing my test with |
@Morikko update your code with the last commit, compile the program and try the instructions below. Open a terminal and call the command below: The variable IconColor should change when you change de icon color. |
@DanielBorgesOliveira Yes, I confirm, update is immediate. |
Hi, thanks for this cool piece of software first of all.
Got it running on Fedora 35 today, now I'm wondering if there's any way to persist the chosen icon color; it's a little less convenient that it changes back to blue whenever a new login is performed.
A switch for the launch script would be most welcome if you're maybe planning for a future version.
The text was updated successfully, but these errors were encountered: