From: James <ja...@pi...> - 2002-04-19 12:03:55
|
On Fri, Apr 19, 2002 at 01:10:40PM +0200, Davide Vide Ferrari wrote: | 19/04/2002 13.01.53, James <ja...@pi...> wrote: | | >On Thu, Apr 18, 2002 at 09:22:36PM +0800, sub wrote: | >| Will xine disable the screensaver ? Or xine won't be effected by | >| screensaver ? | > | >No, and no. | > | >Xine doesn't disable the screensaver as such. What it will do is | >pretend to move the mouse so the screensaver thinks your computer isn't | >idle. | > | >What is currently does is kill XScreensaver, then somehow restart it. | | I don't understand.. | So if I set screensaver after 10 minutes, and I start watching a divx, after | 10' 01" the SS will pop up annoying my peaceful movie vision? No, currently (Xine 0.9.8, and maybe CVS if the patch hasn't been applied yet) Xine kills off XScreensaver, then when you quit Xine it starts it up again. So currently you run Xine and XScreensaver dies. No screensaver pops up (ever again). I wrote a patch to simulate the user pressing the Numlock key every minute. This patch was then modified (and improved) to twiddle the mouse pointer instead. So what happens is the screensaver is still running, but every minute Xine 'nudges' the mouse and the screensaver never starts up. You won't see the screensaver since the mouse is 'nudged' more frequently than your screensaver's timeout is set. THis is cool because it means XScreensaver/whateverSaver never gets killed, and if Xine crashes, your screensaver works again as normal. No more mangled /dev/dvd descriptors or rampant DPMS settings. | If so, why not implement something like MPlayer? I don't run MPlayer, so what does it do? -- There's nothing remarkable about it. All one has to do is hit the right keys at the right time and the instrument plays itself. -- J.S. Bach 6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wn...@cv...t.hx (rot13'd) |