Skip to content
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

use the ubuntu launcher API to populate the correct icon #472

Open
totaam opened this issue Dec 12, 2013 · 3 comments
Open

use the ubuntu launcher API to populate the correct icon #472

totaam opened this issue Dec 12, 2013 · 3 comments
Milestone

Comments

@totaam
Copy link
Collaborator

totaam commented Dec 12, 2013

With unity, the icon shown in the "dock" area is not the one we specify for the tray icon, but it should probably be.

Problems:

  • this is an Ubuntu / Unity thing only (and they've caused us enough pain already)
  • the Python Launcher API is gtk3 only... (gobject introspection) so we would need some simple ctypes wrappers (or Cython, whatever is easiest)
  • the icons we have are probably too low-res to look good in the dock (that's not insurmountable)

See also: #508 and #228

@totaam
Copy link
Collaborator Author

totaam commented Aug 19, 2014

@totaam
Copy link
Collaborator Author

totaam commented Nov 12, 2015

I thought it should be relatively easy to query these menus via dbus, there is an "appmenu registrar" service after all and the interface looks sane, but querying it the path always comes up as "/".
Instead, it looks like we need to look for _UNITY_OBJECT_PATH,

And whilst we're dealing with this, it might make sense to forward appindicators: How does one find out which application is associated with an indicator icon?.

Not for this release.

@totaam
Copy link
Collaborator Author

totaam commented Nov 6, 2017

Hopefully Ubuntu will completely drop Unity and its APIs then we can focus on just one (gnome's): #476.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant