GNOME Bugzilla – Bug 582322
Keyboard shortcut to modify rating of track
Last modified: 2020-03-17 08:25:18 UTC
A shortcut key could be used to modify the rating of the currently playing (or currently selected) track. For example, Ctrl+Shift+1 through 5 to give the track that number of stars. I'd think that the currently selected track would be more useful, but the original request is for the currently playing track. As per http://www.nabble.com/Feature-Request%3A-Global-keyboard-shortcut-to-rate-playing-song-with-%22stars%22-tp22956045p22956045.html
This somehow relates to bugs #560238 and #579754 . Maybe this is a chance to resolve all bugs together.
Bugs as links: bug 560238 and bug 579754
(In reply to comment #1) > This somehow relates to bugs #560238 and #579754 . Maybe this is a chance to > resolve all bugs together. Hm, definitely related, although AFAIK the DBus interface doesn't allow keyboard shortcuts within the application, right?
Is this bug dead or is there a possibility to realize this?
as per bug https://bugzilla.gnome.org/show_bug.cgi?id=579754 there is a dbus interface for the ratings. also there is a cli option to use: banshee --set-rating=RATING(from 0 to 5) eg banshee --set-rating=2 you can try assigning the commands above as keyboard shortcuts with 'gnome-keybinding-properties' if you use gnome. For now (17/02/2011) banshee --set-rating thows an exception, so i can't test it myself either. i hope the exception resolved in future releases.
(In reply to comment #5) > For now (17/02/2011) banshee --set-rating thows an exception, so i can't test > it myself either. i hope the exception resolved in future releases. It's an NDesk.DBus issue, see bug 541279, comment 7.
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.