reopen 330017 tag 330017 fixed-upstream thanks * Adeodato Simó [Wed, 18 Jan 2006 01:41:20 +0100]:
> Upstream's answer to this from http://bugs.kde.org/115379 is: > Guys, I really don't get what this report is about. The collection > update check is executed exactly one minute after startup. Is that a > problem, waiting one minute? > And they closed it; I'm doing the same with the corresponding Debian > bug. But then: ------- Additional Comments From dato net com org es 2006-01-18 01:39 ------- (I respect the decision to close the bug, but personally I feel that one being able to, after adding some files to /mnt/mp3, hit a button and have them instantly appear in the Collection, as opposed that idling 60 seconds over one's thumbs waiting for amaroK to pick them, is a more pleasant user experience.) ------- Additional Comments From kde-dev emailgoeshere com 2006-01-18 19:17 ------- I can see a point here. Now that the collection scanner has been redone and is faster, I've set it to run scanModifiedDirs() on startup *iff* it does not start a scan for some other reason (collection is empty, directories to scan have changed). If nothing has been modified in the directories, it should quit without having taken too much time; otherwise it will read in the new tracks. I think this makes sense, but if people are complaining that it takes too much time to start up now, I'll remove this, and you'll have to wait the 60 seconds. (Note: this will be in amarok SVN, and may or may not be backported to the next 1.3.x release...otherwise it will show up in the 1.4 release.) -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Don't worry about what anybody else is going to do. The best way to predict the future is to invent it. -- Alan Kay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
