Version: 2.3.90 (2.4 beta 1) (using KDE 4.5.4) OS: Linux I really like the new feature that stores play-counts & ratings into files! However, there's an issue: playcount is updated much more frequent than ratings. This leads to extra disk usage & lags when playing music in LAN via NFS. I suggest you to split this option in two: "write play count" and "write rating". Users should be able to choose which one fits better to their needs. Thank you for your work! :) Reproducible: Didn't try Steps to Reproduce: Settings Actual Results: One checkbox "Write statistics to file" Expected Results: A group "Write statistics to file" 2 checkboxes: "play count", "rating"
We had some discussions about cluttering the options dialog and I have already hidden two options to save any metadata to the file and saving images to the file. How about new options that are not shown in the UI but which you can edit via the settings file. A wiki page describing these settings is mandatory of course.
Yep, ability to tune is a must-have feature, especially when it concerns modification of user files! Hidden config options will do the job for me but I'm not sure about other users: usually a GUI app allows to configure everything w/out touching config files. Hidden features may remain totally unnoticed. Maybe, there should be a hint in the tooltip? I'm not a usability expert, however :)
A lot of XMPP clients, due to the complexity of XMPP and the number of options it provides, have an Advanced config area where there are two columns -- option name and option value -- and a description of what the option does underneath somewhere. I can't help but wonder if this would be a good idea for us.
Exactly! My suggestion is to use some tree widget to group `amarokrc` sections. "Name|Value" is ... too GTK-ish :) Amarok works great and everything is just the way it should be, but I always wondered why such a great & complex player has so little options to tune! Maybe, it is time to expose some 'tunable guts' :)
This appears to be a duplicate of Bug 259117.
*** This bug has been marked as a duplicate of bug 259117 ***