xscreensaver 5.00 released

Stick a fork in it: I hereby declare XScreenSaver 5.00 to be good enough.
Tags: , , , ,

26 Responses:

  1. hermeticseal says:

    finally... BSOD! my new black macbook thanks you!

  2. pdx6 says:

    First of all, this is completely awesome. Thank you and everyone who helped debug it.

    I ran into a minor install problem:

    I double-clicked the Anemone screen saver in the disk image to install it so I could test it out, installed only for my user. I then opened the System Preferences and tested the screen saver. Everything was great. I left the "Desktop and & Screen Saver" window open.

    I then followed the rest of the directions to install all the screen savers, that is I did a drag and drop into ~/Library/Screen Saver.

    The "Desktop & Screen Saver" window did not show the new screen savers. Doing a "Show All" followed by going back to the "Desktop & Screen Saver" window still not show the screen savers.

    By closing the System Preferences window, then relaunching it and going to "Desktop & Screen saver" showed all the new screen savers.

    In short, the System Preferences or Desktop & Screen saver window may need to be closed when installing these.

    I know, a stupid problem, but these are users after all.

  3. flipzagging says:

    I'm already a satisfied customer. Thanks!

    (Real programmers have betas measurable in weeks.)

  4. rsdio says:

    I, at first, read that as "Go out and fork it..."

  5. Dang...and just after I got 4.22 installed on my Color Classic. (Thanks for your answer to my email about the colors, BTW. Still haven't got it worked out, but at least I sort of know where to look.) I have to admit that it is a blast getting 0.05 FPS out of some of the OpenGL modules. ☺

    I've noticed xscreensaver locks up on my Ubuntu 5.10 box for some reason, though. Anyone have suggestions on how I could go about troubleshooting it?

  6. mirnephilim says:

    Thank you kindly for the OS X release

  7. Yay! I just started using it a few weeks ago, when I noticed that my LCD screen was burning in (which I thought was impossible). Very much loving it. The reboot hack got me good - is that bsod?

    Actually: is there some way I've missed to find out the name of the currently running hack, besides guessing / looking in the hacks directory / trying some?

    • At least with the X11 version you can start up xscreensaver-demo and the last run hack will be highlighted.

      • Is that saved in a file somewhere for xscreensaver-demo to know that? I can't run xscreensaver-demo on my box.

        • (Assuming unix)
          In ~/.xscreensaver the is a line:
          selected: 96

          This is the offset into the list of screensavers that is also part of ~/.xscreensaver.

        • jwz says:

          "xprop -root". And it's time for you to upgrade from the MicroVax.

          • Heh...gtk2 (at least, maybe other dependencies too) won't compile under NetBSD/mac68k. So I should have said I can't even build it. If it were a gtk1 app, maybe...

            • I thought it would build as a Gtk1 app if Gtk2 was not installed. Oh well, here is a quick Perl script I knocked together to pull the name out of the .xscreensaver file based on the offset stored in the root window.


              #!/usr/bin/perl

              use strict;
              use warnings;

              $/ = "\\n\\";
              my ($hacknum) = qx{xprop -root} =~
              /_SCREENSAVER_STATUS\(INTEGER\) = \d+, \d+, (\d+)/;

              open FH, '< ', "$ENV{HOME}/.xscreensaver"
              or die "Configure xscreensaver first\n";

              my @hacks;
              while (my $line = ) {
              next unless $. == $hacknum;
              print $line =~ m{^-?\s*(?:GL:)?\s*(".*"|\w+)}ms, "\n";
              }
              • HTML is a wonderful thing. The script should be


                #!/usr/bin/perl

                use strict;
                use warnings;

                $/ = "\\n\\";
                my ($hacknum) = qx{xprop -root} =~
                /_SCREENSAVER_STATUS\(INTEGER\) = \d+, \d+, (\d+)/;

                open FH, '<', "$ENV{HOME}/.xscreensaver"
                or die "Configure xscreensaver first\n";

                my @hacks;
                while (my $line = <FH>) {
                next unless $. == $hacknum;
                print $line =~ m{^-?\s*(?:GL:)?\s*(".*"|\w+)}ms, "\n";
                }
            • I take it back. I managed to get gtk2 compiled over the weekend after hacking a Makefile. Working on xscreensaver-demo now...

    • jwz says:

      On Unix, when you bring up xscreensaver-demo, the most-recently-run hack is selected by default. Yeah, all the rebooty ones are bsod.

  8. i am a mac user, and this is my first experience with xscreensaver. it is really amazingly good. it brings a touch of irreverent mischief to my computing experience that i've not had in many years. i particularly like the apple2 one. it cracks me up to notice that the simulated crt guns are occasionally misaligned, resulting in off-color pixels here and there.

    it's kind of sad that this reminds me that i used to think computers were fun. then i spent 15 or 20 years making my living this way, which has thoroughly sapped the joy out of the experience.

  9. The speed slider in IFSMap goes slow when set to fast and fast when set to slow.

  10. feren says:

    XScreenSaver for the Mac was the first application I downloaded after my new black MacBook arrived (Hey, it's pretty as well as functional. Two birds, one stone and all that) three weeks ago. It's a bit belated, but I wanted to pass on a "thanks so much" for all your work on it.

    I also wanted to let you know that I am greatly appreciative for all the other mac tagged entries you've written in the last year or so. It's been exceptionally useful for me in learning what some of the best programs are for various projects.