--- Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> wrote:
I also said there could be exceptions... I agree temporarily disabling the screen saver can be useful, so we probably want to allow at least that. I'm not sure we want to allow messing with the timeout though. Yep, I think the same. Being able to control screen saver activity is pretty damn needed (for DVD/movie players etc.).
I removed affecting X settings because I did not see reasons to keep them. You gave me more than enough.
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.
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, 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? Andriy __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com