also sprach Jamie Zawinski <[EMAIL PROTECTED]> [2007.09.19.1927 +0100]:
That's talking about RANDR, not Xinerama.
Please reread the bug report. It may not be obvious, but Raphaël is
using xrandr, which in turn uses Xinerama. The difference between
the two is that Xinerama was not expected to change at runtime, but
xrandr makes that possible. Hence you need to listen for randr
events to react to them.
Right, I get that. Let me summarize:
1: xscreensaver listens to the Xinerama data provided at launch;
2: xscreensaver already receives and reacts to RANDR
RRScreenChangeNotify events (in driver/timers.c:1010);
3: there is no such thing as a "Xinerama event".
(Sorry if I'm being pedantic about point 3, but these things matter.)
So, if there's something that xscreensaver is supposed to be doing
that it is not, it's not clear to me what that is.
It would be very helpful if someone who has access to multihead X11
hardware that exhibits this problem would take a look at it, because
I no longer have that hardware.
(FWIW, the xscreensaver RANDR support appeared in version 4.16 in May
2004.)
