Bug 164689 - lock plasmoid: show and interact with screensaver settings
Summary: lock plasmoid: show and interact with screensaver settings
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-misc (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-22 19:54 UTC by Maciej Pilichowski
Modified: 2018-06-08 20:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2008-06-22 19:54:18 UTC
Version:            (using Devel)

lock plasmoid: show and interact with screensaver settings

In SS, screensaver module you can set if ss also locks the computer. It would useful if lock plamoid somehow show that setting (small sub-icon "(" of the moon?). It would be also useful having in context menu of lock plasmoid option to switch this.

Reason: it is much faster way to configure this option, and it is good when you like to save time (me). In home, I would use ss without locking, but in institute with it. So I just click RMB on lock, choose "ss auto" (or something) like this, and voila, I get it -- in fast, intuitive way.
Comment 1 Nate Graham 2018-06-08 20:31:42 UTC
Hello!

This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable.

Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham