Bug 398260

Summary: Peruse doesn't remove moved or missing files from its cache.
Product: [Applications] peruse Reporter: wolthera <griffinvalley>
Component: generalAssignee: Dan Leinir Turthra Jensen <admin>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: https://commits.kde.org/peruse/9e643dd233010f147106a65eecece4f5fe5ed3d1 Version Fixed In:

Description wolthera 2018-09-04 17:10:30 UTC 
Dye to Bug 398259 I changed the name, but now there's a bogus file entry in the cache and it won't go away.

Probably related to Bug 398211, which is about the cache not ever refreshing.
Comment 1 wolthera 2018-09-25 14:16:20 UTC 
Git commit 9e643dd233010f147106a65eecece4f5fe5ed3d1 by Wolthera van Hövell tot Westerflier.
Committed on 25/09/2018 at 14:11.
Pushed by woltherav into branch 'master'.

This removes entries from the cache when removing books within peruse,
but also removes entries when QFileInfo::exists() cannot verify they exist(when removed
from outside).

The latter might be a little slower, but not as noticable as the slowness of building the
cache for the first time. If it does become a problem this will be the first place to start
optimising.

Differential Revision: https://phabricator.kde.org/D15748

M  +14   -0    src/qtquick/BookDatabase.cpp
M  +5    -0    src/qtquick/BookDatabase.h
M  +14   -4    src/qtquick/BookListModel.cpp

https://commits.kde.org/peruse/9e643dd233010f147106a65eecece4f5fe5ed3d1