After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331886 - Screensaver should allow "selective random"
Screensaver should allow "selective random"
Status: RESOLVED DUPLICATE of bug 316462
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.13.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-20 11:48 UTC by Daniel Holbach
Modified: 2006-02-20 16:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Holbach 2006-02-20 11:48:39 UTC
Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnome-screensaver/+bug/31979

I would like it to be possible to be selective about which screensavers gets to be in the random list. I have a few favourites but currently it is all or nothing.

A simplistic way to implement this would be to simply allow CTRL-selecting in the screensavers list, see attached screenshot for mock-up. It's not totally discoverable but OTOH it was the first thing I tried... and it could be mentioned in the help for those who look for it. Those who don't look for it will never notice.

A further step would be to have a separate GUI for this, but I'm note sure if it's needed. An even better way to do it would be to introduce checkboxes, that way individual screensavers could be previewed while retaining the list.

--

http://librarian.launchpad.net/1577144/Screensaver_Preferences_Multiple_Random.png (Mockup of multiple selection)

The preview screen turns to an informational banner, in case someone happens to do this by mistake. Could include some simple instructions too.
Comment 1 William Jon McCann 2006-02-20 16:42:06 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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