Bug 139532 - random option for each screen saver category
Summary: random option for each screen saver category
Status: RESOLVED DUPLICATE of bug 57572
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-03 00:53 UTC by Jeff Wingstrom
Modified: 2008-05-19 17:59 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 Jeff Wingstrom 2007-01-03 00:53:37 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc (GCC) 4.1.2 20061028 (prerelease) (Debian 4.1.1-19) 
OS:                Linux

It would be good if the "random screensaver" (is this a screensaver, or an option?) would allow me to select which category of screensavers to pull random screensavers from.  Selection and de-selection of screensavers within the category would be fine too, but isn't a big issue to me.

As a side note, it would be great if when in random mode, there would be a way to find out what screensaver is running.  An option to have the name of the currently running screensaver displayed would work.  I know that there may be implementation difficulties with this option, since it would have to display the name while another application is writing over all other applications and over the full screen.  It would also be good if it moved the information around the screen to further curb "burn in".  If this is too big of a problem, a splash screen that had the names of the last screensaver and next one during "changeover" would work.  Being able to access a list of "last screensavers run" would work too.

The current version is great (just trying to help make it better).

Thanks.
Comment 1 Oswald Buddenhagen 2007-05-18 23:28:28 UTC
regarding your "side note": i don't see much chance of this getting implemented. if you insist, open a separate report - not that it would enlarge the chances ...

*** This bug has been marked as a duplicate of 57572 ***