From: P.G. R. <p.g...@ph...> - 2007-07-23 22:14:27
|
On Monday 23 July 2007 06:44:04 Tino Keitel wrote: > On Mon, Jul 23, 2007 at 07:39:45 +0200, Tino Keitel wrote: > > Hi folks, > > > > with the current gtkpod from the gapless branch (svn rev 1648), I added > > an album without a cover to the database. Then I downloaded a cover. > > After a "Sync playlist with dirs", there is no cover shown for this > > album. Is this intended? I can't remember if this worked with older > > versions. > > I forgot to mention that I also checked the cover after restarting > gtkpod, it was still missing. > > Regards, > Tino > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Gtkpod-questions mailing list > Gtk...@li... > https://lists.sourceforge.net/lists/listinfo/gtkpod-questions HI Tino, Had a look at your comments and have made the following changes to the trunk. If they seem okay then we can merge them with the other branches (gapless and photo). - Changing the cover of all tracks in an album through the details window will update the coverart display to show the new cover. - Clicking on "update tracks from file" will refresh the artwork for the selected tracks whether the artwork has changed or not (some if clause to detect whether the artwork has changed might be an improvement on this at some point). - Have messed about with the "sync playlist with dirs" function it wasnt apparent how I could know whether a track had been updated or even whether any components in the gtkpod display are updated with new info. Any thoughts on this from anybody welcome. After all, if a pm_track_changed occurs somewhere then all the affected tracks need are a extraTrackData->tartwork_changed = TRUE and the coverart display should update accordingly. Hope this helps. Regards PGR -- P.G. Richardson Email: p.g...@ph... |