https://bugs.kde.org/show_bug.cgi?id=478582
--- Comment #2 from Frank <[email protected]> --- (In reply to Niccolò Venerandi from comment #1) > This is already possible with the scripting API: ConfigFile() can open > Plasma's own config file, and nested groups are made by passing a parent > ConfigFile instead of a file name. For example: > > var plugins = ConfigFile('plasma-org.kde.plasma.desktop-appletsrc', > 'ActionPlugins'); > var desktop = ConfigFile(plugins, '0'); > var rightButton = ConfigFile(desktop, 'RightButton;NoModifier'); > rightButton.writeEntry('_logout', true); > rightButton.writeEntry('_lock_screen', true); > > This writes exactly [ActionPlugins][0][RightButton;NoModifier], and the > desktop context menu shows those actions the next time Plasma starts. Yes I found that out a while back, thanks for confirming I am doing it the right way! It does show only on next Plasma start, I could not figure out the command to execute so that it shows immediately as if the user would set those configs manually through the UI and click APPLY. But that is a small compromise and we accepted without issue for our ISOs. :) -- You are receiving this mail because: You are watching all bug changes.
