Summary: | Global shortcut for last.fm (skip/love/ban) | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Krisztian Vida <vidakris> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | acocaracha, david.nolden.kde, florent, gsasha, ivo, kfunk, marcin.gil, skywalker_99 |
Priority: | NOR | ||
Version: | 1.4.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Krisztian Vida
2006-10-24 13:56:36 UTC
*** Bug 138322 has been marked as a duplicate of this bug. *** *** Bug 134659 has been marked as a duplicate of this bug. *** Seconding this, too. Thirding! Would be a very nice feature. This is probably closely related to bug #138591 (which proposed a dcop call for the same thing). *** This bug has been confirmed by popular vote. *** Amarok 2 has a global shortcut for loving to last.fm: Love: Meta+L. We haven't added shortcuts for skip and ban, but perhaps we will in the future (so far we decided against it). Closing bug since it's fixed from our perspective - skip/ban shortcuts are a wontfix currently. Shortcuts for Ban/Skip would be great. What is the objection against it? If you're worried about too many shortcuts, maybe it would make sense to merge this with the general "rating" system. WIN+5 could equal "loving", WIN+0 could equal banning, WIN+1 would equal skipping or something like that. *** Bug 178017 has been marked as a duplicate of this bug. *** Whats the Staus here atm? Is there a specific reason why not to implement that? I wonder why, guess it wont be so much amount of work to give that Button a shortcut. Greets Jochen, you are welcome to submit a patch, then, but I think we really have so many more important things to implement. commit 871dc03e95a6b5d4bb91588b5b9ea3b45e7ad7e7 Author: Kevin Funk <krf@electrostorm.net> Date: Thu Oct 1 23:12:20 2009 +0200 Make Love/Skip/Ban available in shortcuts configuration dialog. BUG: 136232 *** Bug 179536 has been marked as a duplicate of this bug. *** |