-
-
Notifications
You must be signed in to change notification settings - Fork 40
Failed to bind shortcut #45
Comments
Typically bindings fail due to another application taking the existing bindings. Be sure to close out of any other applications that might steal those bindings first (e.g. music players, browsers) |
This is still an issue. The mediaplyapause shortcut is bounded by the OS, so I can't quit it in order for this app to get the binding first. |
Ah, sorry I misunderstood your question. We support choosing alternative media key shortcuts via our Preferences window (menu bar -> File -> Preferences) |
That's a good workaround but the issue is still there. I would like to control this player like I control any other one. In the meantime, I'll have to change the shortcuts. |
I understand your experience/frustrations but I don't think there's much we can do:
Since our application is still CLI based, I think the "WARN" console messages at startup surface this info the user pretty well for now |
@twolfson I've submitted a patch for this issue in another project headsetapp/headset-electron based on this file Google-Play-Music-Desktop-Player-UNOFFICIAL-/mediaKeysDBus.js |
While that functionality works with a single app, I believe it would cause multiple music apps listening to DBus to receive the same event and start playing thus defeating the purpose |
From my experience, the command |
Ah, I think I understand now. I'm currently swamped with other priorities at the moment. I'm going to reopen this issue and mark it as "Help Wanted". Any PRs are welcome |
Great! I'll try to get a shot at it if I have time and submit a PR, but I'm also busy at the moment. |
When loading the app from console, I get the errors:
And because of this, I can't use my media keys to control the app. I don't have MPRIS and I don't want to install it and/or use it.
I'm running the app on Ubuntu 16.04, node v6.11.1, npm v3.10.10
The text was updated successfully, but these errors were encountered: