To better integrate the applications with the user's theme and make it a part of user's customization. The recommendation is to use just the icon name without the full path.
Putting the full path on it make the icon "hardcoded" in other words it will not allow to use application icon from the icon theme if it exist.
As example, the project Numix who make excellent icon themes made a "LinSSID" icon to fit it into Numix style. But it's only possible to use it if it uses the relative path into .desktop file. The issue inside them bug report can be found here: https://github.com/numixproject/numix-icon-theme-circle/issues/1313
However the solution is very simple (based on LinSSID 2.7 source):
First rename the icon files because the linssid.png will be default instead of linssid48.png or just uses the 64x64 version and ignore the following two lines:
rename linssid-app/linssid.png to linssid-app/linssid64.png
rename linssid-app/linssid48.png to linssid-app/linssid.png
Inside linssid.desktop remove the full path /usr/share/pixmaps/linssid48.png and substitute it for linssid instead.
The system will locate your icon anyway but help us to better customize our desktop :)
linssid-app/linssid.desktop:
Icon=/usr/share/pixmaps/linssid48.png
Icon=linssid
Questions? Let me know!
Regards,
Last edit: Henrique Lechner 2015-03-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the tip. I will incorporate it into the next release. That's underway but is taking a good deal more effort than originally imagined. My goal is to completely rewrite the data acquisition portion to make use of netlink and NL80211. That's not so easy. There's essentially no documentation and the examples (iw) could be poster examples of arcane, uncommented, unfathomable "c" code. Anyhow, I have a handle on it and it's progressing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi There,
To better integrate the applications with the user's theme and make it a part of user's customization. The recommendation is to use just the icon name without the full path.
Putting the full path on it make the icon "hardcoded" in other words it will not allow to use application icon from the icon theme if it exist.
As example, the project Numix who make excellent icon themes made a "LinSSID" icon to fit it into Numix style. But it's only possible to use it if it uses the relative path into .desktop file. The issue inside them bug report can be found here:
https://github.com/numixproject/numix-icon-theme-circle/issues/1313
However the solution is very simple (based on LinSSID 2.7 source):
Questions? Let me know!
Regards,
Last edit: Henrique Lechner 2015-03-12
Thanks for the tip. I will incorporate it into the next release. That's underway but is taking a good deal more effort than originally imagined. My goal is to completely rewrite the data acquisition portion to make use of netlink and NL80211. That's not so easy. There's essentially no documentation and the examples (iw) could be poster examples of arcane, uncommented, unfathomable "c" code. Anyhow, I have a handle on it and it's progressing.