Bug 79549 - is it possible to have mp3s displayed in a different colour if their tag has been modified? (+ undo and save-all buttons)
Summary: is it possible to have mp3s displayed in a different colour if their tag has ...
Status: RESOLVED DUPLICATE of bug 61340
Alias: None
Product: juk
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-13 10:26 UTC by Caoilte O'Connor
Modified: 2004-04-13 10:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caoilte O'Connor 2004-04-13 10:26:10 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages

It doesn't have to be a very different colour, but it would be nice if I could tell whether changes I've made to an mp3 tag are written to disk yet.

I don't even know if internet/filesystem guessing changes are written automatically. If they were a different colour once guesses had been made and you had to save the mp3 that would seem more natural (to me at least).

If you had to explicitly save an mp3 tag's changes (and some sort of save-all seems quite reasonable) there is less scope for correcting occasional accidental changes.

You could then also add an undo button. 

Sorry, these features may seem quite unnecessary but fit the way I've come to expect windows/kde/unix gui apps to work. It's quite unsettling not to be able to save changes/undo etc.
Comment 1 Scott Wheeler 2004-04-13 10:41:24 UTC
Actually they're generally done as soon as you make them with the exception of when using the "extended" tag editor in which case you're prompted when you change files.  (Which doesn't leave much time for marking them different colors.  :-) )

As for the undo, it's been planned for a while, but it's non-trivial.  I hope to have it done for KDE 3.3.  But since that one's already reported I'm marking this as a duplicate of it.

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