https://bugs.kde.org/show_bug.cgi?id=473088
--- Comment #16 from off...@hantsch.co.at --- The absolutely bullet proof method would be to go to next element in Lizzy. of anything happens (locked, not found, whatever), reload the file list from scratch and proceed. Even this can be enhenced. ALWAYS reload the file list before NextSlide. This way there exists always a valid list of files. Them increment the index. If it gets behind momentary list of files, set it back to first element. This method also allows increasing the list of pictures on the fly, because additional files may cause some confusion in one cycle (if new files get inserted before current index, but after reaching the end of list, it will work smoothly again. Am 15. August 2023 16:16:50 MESZ schrieb Fushan Wen <bugzilla_nore...@kde.org>: >https://bugs.kde.org/show_bug.cgi?id=473088 > >--- Comment #14 from Fushan Wen <qydwhotm...@gmail.com> --- >Git commit bb17444cbab7d76b18c9c4bf2294d3e87426fc6b by Fushan Wen. >Committed on 15/08/2023 at 16:16. >Pushed by fusionfuture into branch 'Plasma/5.27'. > >wallpapers/image: fix potential invalid slide index in `nextSlide` > >If the last wallpaper is deleted before `nextSlide` is called, the next >time `nextSlide` is called, m_currentSlide is always increased by 1, >which is an invalid index, causing the slideshow always stuck at the >last wallpaper. > > >(cherry picked from commit e69e0a936c2a6ae6790e5ff8ddffdf7f0539a97b) > >M +1 -1 wallpapers/image/plugin/imagebackend.cpp > >https://invent.kde.org/plasma/plasma-workspace/-/commit/bb17444cbab7d76b18c9c4bf2294d3e87426fc6b > >-- >You are receiving this mail because: >You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
