Hi,

> I think it could be problematic for the user having newly fetched lyrics
> saved automatically over the old ones, a user can easilyhit reload more or
> less accidently and lose changes he may have made to the cached lyrics.
> I think it would be better just to split the "edit/save" button in 2
maybe a "Do you really want to re-fetch lyrics (old ones will be overwritten" 
message would also do it - but that violates the string-freeze.

> different ones, which would enable one to overwrite cached lyrics with the
> fetched ones without having to press "edit", and the former "save" part of
> the edit button could be used to stop editing without saving changes (which
> can't be done currently).
that might be a nice idea - I just don't know what's best for usability there

Regards,
Martin
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel