After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554713 - there is no way to toggle playback from outside
there is no way to toggle playback from outside
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Playback
git master
Other Linux
: Normal enhancement
: 1.6
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-02 14:49 UTC by daniel g. siegel
Modified: 2009-01-21 21:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
add help line to help output (965 bytes, patch)
2008-11-01 14:15 UTC, daniel g. siegel 		committed Details | Review

Description daniel g. siegel 2008-10-02 14:49:22 UTC 
banshee --help-playback does not show any option for toggling (pausing) the playback and then resume.

this would be great for people handling with ir-devices and similar stuff
Comment 1 Andrew Conkling 2008-10-02 22:36:33 UTC 
Seems like we need a `banshee --playpause`.
Comment 2 daniel g. siegel 2008-10-03 14:00:39 UTC 
enhancing --pause to continue if banshee is in pause state would be enough
Comment 3 daniel g. siegel 2008-11-01 14:15:09 UTC 
Created attachment 121782 [details] [review]
add help line to help output

my fault, the action was already there and parsed, the devs just missed it to add it to the help output
Comment 4 Bertrand Lorentz 2008-11-03 21:11:36 UTC 
Good catch, thanks for the patch !
Next time, please remember to create the patch from the directory containing src/. ;)
Comment 5 daniel g. siegel 2008-11-03 22:57:22 UTC 
you just can use 

patch -p1 < somepatch 

to remove the first leading directory.
Comment 6 Gabriel Burt 2008-12-29 22:33:08 UTC 
We're in a string freeze until after 1.4.2
Comment 7 Bertrand Lorentz 2009-01-21 21:45:33 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.