http://bugs.gpodder.org/show_bug.cgi?id=293
--- Comment #3 from Justin Forest <[email protected]> 2009-01-14 20:04:31 --- The right solution is to save the database whenever the data is updated, but not during a massive operation. Doing this repeatedly slows things down not only on maemo, but on other low end hardware, such as EEE PC. That's why we originally postponed the updates. I don't think this is a major bug when you use brute force to kill an application and some things fall apart, but this certainly is an issue. I think the database needs to be explicitly updated after: - an episode is downloaded, - something is done to episodes with a pop-up menu, or - a channel is updated. I don't think a timeout based solution would work. -- Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
