Hi Jamie! You wrote:
> Did you test what happens if nscreens remains 0 for some length of time, > e.g., through another idle cycle? I'm guessing the answer is "nothing > good"... Yes, I tried, and everything works fine (i.e., nothing happens, and xscreensaver doesn't crash). I also tested several different setups: - starting with two screen, start xscreensaver, remove the second screen, activate xscreensaver - start with one screen, start xscreensaver, add an extra screen (both as an extension and a clone of the currect screen), and activate xscreensaver - start with one screen, start xscreensaver, add an extra, partially overlapping screen, actiavte xscreensaver. In each of these cases, everything works fine as one would expect, and xscreensaver doesn't crash. > It's hard to tell just by looking at it, but I suspect that, for > example, with that change it's going to be running hacks on screens that > no longer exist. (This may actually be true any time the number of > screens is reduced, even when reduced to non-zero.) That doesn't seem to be the case, or at least, it is not bothered by it. Kind regards, Bas Zoetekouw. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
