[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 112972] next track doesn't advance when file does not exist
From:       Tim Middleton <x () vex ! net>
Date:       2005-09-21 13:55:50
Message-ID: 20050921135550.29536.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=112972         




------- Additional Comments From x vex net  2005-09-21 15:55 -------
Interesting. So the real bug is that if amarok is allowed to skip tracks it freezes \
the UI... is there a bug in the tracker for that? If not, consider this it? (-: Does \
sound like something that could use fixing one way or another. 

Could not a simple fraction of a second delay between skipping give up time to the \
UI? If it were so simple, no doubt someone would have done it. Even a whole second \
delay. Call it punishing the user for deleting queued tracks... if 1000 tracks \
disapear they must wait 16 minutes before the next one is found. (-:

But we are talking about edge cases for all of these situations. 

Is it more likely a directory with hundreds of files is removed, or single file, or a \
dozen files...

On the condition that a file is not found, the containing directory could be looked \
for... if it is not found, all files in that path removed from queue. 

Hmm, just some thoughts. Though it sounds like these thoughts may have already been \
had.


[prev in list] [next in list] [prev in thread] [next in thread]