Skip to content

Fix synchronization issues on first run after resource directory change

Sharaf Zaman requested to merge szaman/krita:sh-zam/resource-system-bugs into master

Test Plan

From: U: Resource folder and cache

Make a new custom resource, change the location of the resource folder to some non-standard and empty location (but don’t change the cache location).

NO, on the first boot after the resource folder change, the cache points to resources from the previous location.

This shouldn't be reproducible anymore.

Formalities Checklist

  • I confirmed this builds.
  • I confirmed Krita ran and the relevant functions work.
  • I tested the relevant unit tests and can confirm they are not broken. (If not possible, don't hesitate to ask for help!)
  • I made sure my commits build individually and have good descriptions as per KDE guidelines.
  • I made sure my code conforms to the standards set in the HACKING file.
  • I can confirm the code is licensed and attributed appropriately, and that unattributed code is mine, as per KDE Licensing Policy.

Merge request reports