From: Todd Z. <tm...@po...> - 2007-06-20 15:25:40
|
P.G. Richardson wrote: > Hmmm ... all possible solutions. Damn users always wanting it all. ;) > I think a check would be useful to put back in there because it is > obviously annoying and slow to recopy the artwork. At the time I was > trying to fix the original bug and knew the current test just > wouldnt be valid anymore, ie. filename can be the same even though > there is a new file :-). Does the update_track_from_file function in src/file.c catch this sort of change? If it does, can it be called whenever fetchcover updates the coverart? If not, should that function be updated to catch this sort of change? > Timestamp or sha1hash might work although a record of the original > would be required for comparison? Yeah, I haven't looked closely to see how the code works. I don't know if there's a good place to grab the hash or timestamp of the original artwork. > Is there a hash function I can call on the image file and then store > the result? There are sha1_hash_on_* functions in src/sha1.c. Though a timestamp might be easier and should be sufficient. > Retraining is naturally the most difficult as bad habits are for > life not just for Xmas!! Yeah, I am very much a creature of habit. :) --=20 Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Life is the art of drawing sufficient conclusions from insignificant premises -- Samuel Butler |