- User Since
- Tue, Mar 24, 10:04 AM (4 d, 13 h)
Wed, Mar 25
My bad, I'll look into doing this on Gitlab later today!
Oh, my bad, sorry! I'll look into it later today :)
Tue, Mar 24
I can't look into this any further today maybe, but here's what I have so far. There's still that bug that I mentioned in the previous message, as well as the changes not being reflected immediately.
Humm, I'm getting a bit of strange behavior. If I alter any settings, and then reset the configurations, everything in the 'kritarc' file is deleted EXCEPT the changes done BEFORE resetting the configurations. Any clues?
I was using the already mentioned function 'askClearConfig()' on KisApplication. It does in fact delete the kritarc file from '.local/share/krita', but not the correct file. After switching to your line, it works! It requires a restart to apply theme changes though, so I have a feeling that I'm still missing one last piece of the puzzle. After that I'll create a PR!
Okay, so I made some good progress, and there's a button in the settings to reset the Krita configurations. However, there's something strange, the code says that the file 'kritarc' is located in '.local/share/krita/', where in fact it is stored in the '.config' folder. Any pointers as to how you want this addressed (puns not intended)?
I can try to do this issue, but this is my first time looking at Krita code, and my C++ is a bit rusty, and my Qt skills are non-existent. Still, should be an interesting challenge, if you guys don't mind!
I think that a new option in the Settings tab with a confirmation prompt would suffice. I also agree that a way to access crash logs would be really useful. Something like a pop-up showing the latest 10 crashes, maybe?