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 543350 - Provide a user configurable file management interface in Banshee
Provide a user configurable file management interface in Banshee
Status: RESOLVED DUPLICATE of bug 404827
Product: banshee
Classification: Other
Component: general
git master
Other All
: Normal enhancement
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
: 574507 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-07-16 22:28 UTC by Stephen Holmes
Modified: 2009-05-30 23:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephen Holmes 2008-07-16 22:28:54 UTC
It would be very useful if Banshee provided more user-specified flexibility on where it located its various media files.  I would like to propose the following enhancement...

1.  In the Tools/Preferences tab add an additional dialog tab for
        "Files"
        2.  Allow the user to configure paths for...
           a.  Music
           b.  Audio/Video podcasts
           c.  Movies
           d.  Cover Art
        3.  The default would be to have them cascaded under the Music folder.
        4.  We could even consider a "Backup..." button for the content
Comment 1 Richard Venneman 2008-07-21 19:41:57 UTC
Sure sounds good. Second.
Comment 2 Alexander Kojevnikov 2009-03-07 23:49:06 UTC
*** Bug 574507 has been marked as a duplicate of this bug. ***
Comment 3 Ivanov 2009-04-26 09:18:43 UTC
Just one question. Is there a way like in wine's bugtracker
to vote for bugs. Because I really like this idea and would like
to vote for it. Thanks.
Comment 4 Alexander Kojevnikov 2009-05-30 23:36:15 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 404827 ***