Forgetful podcast manager?

[Bart Cerneels]

This is a result of not stopping the scan of the feed in setXml after 
[purgeCount] items. Since before this commit we removed purged episodes from 
the db those are added again and hasNew is set true. So the new episodes are 
actually old episodes that are beyond the purgeCount boundary. Good new is it 
should only happen once after upgrading and updating the feeds.

So, as we disscussed on irc, let's not remove episodes from the db but only 
from disk (is downloaded) when purging and only show the [purgeCount] most 
recent episodes in the playlistbrowser.
I also have a possible fix for the "podcaster made a mistake and fixed it in 
the same rss-item"-problem (pffff). The way it works now, Amarok doesn't see 
those changes unless they are severe (like a changed guid). I propose a 
hasXml-function that changes the items in the db if there was a correction. 
We'll need some extensive testing on a lot of feeds though.

Greets, see you on irc

On Sunday 23 July 2006 11:00, Seb Ruiz wrote:
> I'll look into this - since i've been playing around with it lately.
> Could you please provide some feeds where this is happening?
>
> thx
> seb
>
> Quoting Mark Kretschmann <markey at web.de>:
> > On Saturday 22 July 2006 18:46, Matej Cepl wrote:
> >> using yesterday's SVN I have podcast manager in weird state. Some feeds
> >> show that they have fresh items, but when you open them they have none,
> >> and even when I mark the particular stream as read, after update it
> >> again claim that there are new items.
> >
> > Same for me. Also the episodes are in random order. FUBAR.
> >
> > --
> > Mark
> > _______________________________________________
> > Amarok mailing list
> > Amarok at kde.org
> > https://mail.kde.org/mailman/listinfo/amarok