[Portland] xdg-screensaver.in

[Bryce Harrington]

On Wed, May 10, 2006 at 08:15:37AM -0600, Aaron J. Seigo wrote:
> On Tuesday 09 May 2006 18:15, Bryce Harrington wrote:
> > If not, should I make a little one to include with xdg-utils? 
> 
> makes sense imho.

Okay, I'll add this to my todo list, but probably won't get to it for a
while.  Meanwhile, I'll get this script committed and add it to the
makefiles and such.  (I'm _still_ waiting on an ssh key to get set up on
freedesktop.org, but hopefully that'll get taken care of one of these
days.)

> > Obviously, it'd be in C, so I'm not sure if that's keeping 
> > with the "just scripts" philosophy, but it'd only be used by the test
> > harness.  (Although, on reflection, if there isn't any other existing
> > way to query the screensaver state, that might actually be a very handy
> > feature for apps to gain from xdg-screensaver.)
> 
> yes, this is apparently on the roadmap from my discussion with people involved 
> with x.org

One other comment, if they're going to be doing a rework, is that it
would be handy to have 'xset q' allow you to specify the parameter you
want.  KDE's dcop approach is much simpler to script in this respect.

> > > talking to one of the kde/x.org guys (frederik), he noted that while this
> > > works it's pretty hacky and that at some point it needs to be fixed
> > > properly in x.org. they've recently added the ability to programmatically
> > > (and safely) block the screensaver w/out resorting to doing things like
> > > faking key events, but even that hasn't made it into an official release
> > > yet. xscreesaver is still a bit of a mess =)
> >
> > I haven't tested xdg-screensaver super thoroughly, but so far it looks
> > like it is able to suspend the screensaver effectively, without faking
> > keyboard events.  (I did run across some C code that'd do this, though,
> > but left that a plan B for now...)
> 
> as waldo pointed out this is pretty suboptimal and what is more often needed 
> is a way to temporarily suspend it (e.g. during a presentation, video, etc) 
> with it automatically coming back on once that event is completed (complete 
> with safety for application crashing). pragmatically it's probably as good as 
> it'll get using the scripts-only method. 
> 
> -- 
> Aaron J. Seigo
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
> 
> Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)



> _______________________________________________
> Portland mailing list
> Portland at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/portland