-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use existing thumbnail cache folder #168
Comments
Try In order to make it persistent do This digs a hole in the sandbox so it may not be an acceptable default. |
Thanks, that does work on an individual basis - I guess my thought was that this seemed like a desirable default because: Gwenview already has I might be misunderstanding part or all of that, apologies for the wasted time if that's the case - but mostly trying to think of what the future state uses will be for this Flatpak, and it seems like a nice efficiency gain to not have to calculate and store multiple copies of the thumbnail cache. |
For apps that have |
Grant access to thumbnail cache folder in home directory. This is safe as Gwenview already has access to everything (host) right now as it's not fully portal aware yet. Fixes: #168
Sounds like a good idea. Made #169 |
Grant access to thumbnail cache folder in home directory. This is safe as Gwenview already has access to everything (host) right now as it's not fully portal aware yet. Fixes: #168
Hi - is it possible to have the Gwenview Flatpak point at the same location as the user's main thumbnail storage,
~/.cache/thumbnails
, so it doesn't have to regenerate new thumbnails for each file/folder with which it's used?The text was updated successfully, but these errors were encountered: