Notes:
1) SPI_GET/SETSCREENSAVETIMEOUT actions processing is
currently independent from X settings.
Waiting for end of discussion about
SystemParametersInfo to implement the integration or
remove corresponding user driver function.
2) SPI_GET/SETSCREENSAVEACTIVE is integrated with X
settings. I take/get data directly from X, there is no
need for using registry to store the value.
Q: It is still necessary to save the data to the
regitry branch for windows applications which access
registry instead of using SystemParametersInfo?
Note, even if the changes are saved to registry
such applications still can have problems because the
registry branch does not exist until the first change.
Change log:
SystemParametersInfo. Implemented processing for
actions SPI_GET/SETSCREENSAVETIMEOUT,
SPI_GET/SETSCREENSAVEACTIVE,
SPI_GET/SETSCREENSAVERRUNNING.
Andriy Palamarchuk
__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
Attachment:
spi_screensave2.diff
Description: spi_screensave2.diff
