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 623715 - Non-default file name patterns.
Non-default file name patterns.
Status: RESOLVED DUPLICATE of bug 319024
Product: sound-juicer
Classification: Applications
Component: interface
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-07-06 22:44 UTC by Andreas Herrmann
Modified: 2015-11-27 11:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch contains my changes to sj-prefs.{c,h} and to sound-juicer.ui (8.01 KB, patch)
2010-07-06 22:44 UTC, Andreas Herrmann
none Details | Review

Description Andreas Herrmann 2010-07-06 22:44:13 UTC
Created attachment 165386 [details] [review]
Patch contains my changes to sj-prefs.{c,h} and to sound-juicer.ui

I think it should be possible to define non-default path and file name patterns in the preferences dialog. Having to change the patterns with the gconf-editor is a little bit annoying.

I replaced the corresponding GtkComboBoxes by GtkComboBoxEntries and changed the corresponding code in sj-prefs.{c,h}. The combo boxes still contain the hard-coded default settings but it's also possible to enter an individual pattern.
The individual pattern is then stored in the gconf-key.
The attached patch is against the latest git master branch.

I'm not very experienced in GTK development, so I'm not sure whether I did this correctly.

Furthermore, it would be nice to have a small legend of the pattern codes (e.g. "%ta - Track Artist") in the preferences dialog. My first idea would be a simple label under the combo boxes, but maybe this makes the dialog too big.

So, tell me what you think about this, please.
Comment 1 Phillip Wood 2015-11-27 11:20:08 UTC

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