https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #5 from Oded Arbel <o...@geek.co.il> --- (In reply to Nate Graham from comment #4) > Depends on how much we want to prioritize avoiding writes to the config > file, I guess. If the user does something silly like change their wallpaper > every 5 seconds, we could end up doing a lot of writes. Is writing the config file every 5 seconds an issue? The config file is synced for a lot of other things - such as moving widgets. When someone is setting up a new widget on their desktop, the config file will be updated multiple times during that process. If the user does RMB -> next wallpaper, again and again - it is user interaction and updating the config file in response seems like an appropriate measure. > So it depends at least partially on how much we care about this use case. Well, obviously _I_ care about this use case 😅 I have a lot of wallpapers and a bunch of automation tools that help me manage them and they interact with the plasma shell using DBus and shell scripting - I'm not actually reading the config file, but both DBus and shell scripting use the same mechanism that - at least with the current code AFAIK - won't update unless we do `KConfigPropertyMap::writeConfig()`. Some of those tools are presented as desktop widgets, so when the wallpaper changes (due to either timer or actually doing "Next wallpaper") I'd expect the widget to reflect the current wallpaper. -- You are receiving this mail because: You are watching all bug changes.
