SystemParametersInfo: Screen Save actions
andi at rhlx01.fht-esslingen.de
Fri Nov 16 14:04:24 CST 2001
On Fri, Nov 16, 2001 at 11:54:36AM -0800, Andriy Palamarchuk wrote:
> > What is *not* needed is some stupid Windows program
> > messing with my
> > nicely configured timeouts :)
> Would you mind about messing the settings temporarily
> :-) I'm going to implement integration in such way
> that the changes to settings from Wine will be only
> temporary - while single X session.
> If user wants to have it permanently he/she should
> change X configuration.
Hmm, it's only possible temporarily anyway ! (current X session !)
Wine will never be able to modify X11 settings in general !
So we have three ways of doing it:
a) Simply don't care about screensaver timeout
b) always set screensaver timeout when requested
c) make X11 controlling behaviour configurable
a) would be ok, b) would be terrible IMHO, and c) would be desireable
I'd let Alexandre vote about whether to use a) or c), though ;)
> > We should probably output a warning message
> > informing the user that we won't
> > modify the timeout, though.
> There will be very many such messages. I would not
> like to do that - useful Wine output can be lost.
Hmm, why ??
You could silence it by using a static boolean or so in case programs set
it too much.
> > Hmm, again, could someone fix the horrible bug in
> > SPI_SETSCREENSAVERACTIVE ?
> > This one leads to pretty stupid blanking in both
> > movie players and,
> > more importantly, InstallShield installers !!
> > Andriy ?
> > (or should I fix it ?)
> I'm on my way :-) I think I'll finish until Monday.
> Will be any suggestions about existing strategy of
> integration with X settings?
Again, maybe make it configurable...
"ModifyX11" = "Y"
and if it's set to N, then only modify "safe" settings.
(hmm, a better name for this variable ?)
Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany
Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/
More information about the wine-devel