[shell-coding] Re: Determining screensaver stats
- From: Christoffer Sjöberg <christoffer.sjoberg@xxxxxxxxxx>
- To: <shell-coding@xxxxxxxxxxxxx>
- Date: Tue, 9 Jul 2002 09:56:30 +0200
I had found that article before, but it doesn't cover win2k or xp.
It still seems as if the events reset the timer there as well,
so I added a max flash count and then disabled all flashing
if systray can determine that a screensaver is running.
// Vendicator
----- Original Message -----
From: "Pavel Vitis" <pvitis@xxxxxxxxx>
To: "Christoffer Sjöberg" <shell-coding@xxxxxxxxxxxxx>
Sent: Tuesday, July 09, 2002 8:52 AM
Subject: [shell-coding] Re: Determining screensaver stats
> > In the latest systray version that I did I included
> > scroll lock flashing on icon updates using keybd_event().
> > However using this method it seems that my
> > screensaver doesn't start ...
>
> > So now two different ideas come up on how to bypass
> > this: either use SendInput instead (don't know how the
> > screensaver responds to this either though)
> > or add a disable flash when the message that the screensaver
> > has started is passed ...
>
> I think that screensaver will never start because any key-press (even
> simulated) will reset idle timer.
>
> There is some reading on this:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;q201833
>
> I think that only way how to manipulate keyboard LED without sending
> actual keystroke is direct access to KB port. So you would probably
> need to create VXD for that.
>
> regards
> ---
> Pavel Vitis
> mailto:pavel.vitis@xxxxxxxxx
> http://come.to/lsg/
>
>
> __________________________________________________
> Subscription options and archive:
> //www.freelists.org/list/shell-coding
>
__________________________________________________
Subscription options and archive:
//www.freelists.org/list/shell-coding
Other related posts:
