Mercurial > pidgin.yaz
diff COPYRIGHT @ 9417:9f6a28af7164
[gaim-migrate @ 10232]
" IDLETRACK.DLL uses Windows hooks to record the last
time the user pressed a key or moved the mouse.
Windows hooks are a bit unfriendly in that they force
the hook DLL into every process - so IDLETRACK.DLL
gets added to every process after Gaim runs. This can
mean that IDLETRACK.DLL doesn't get unloaded when
Gaim stops, which causes a warning about being unable
to write to IDLETRACK.DLL if you then upgrade Gaim.
Further, hooking is a common tactic employed by key
loggers. If the user has a program installed that checks
for global hooks then it will warn the user that Gaim may
contain a key logger.
From Windows 2000 onwards Microsoft introduced an
API function called GetLastInputInfo that returns the
timer tick at the point that the user last pressed a key
or moved the mouse. I have changed idletrack.c so that
it will try to use this if it can, which avoids all the
ugliness of having to use hooks, but it will fall back to
using hooks if the function isn't present.
This patch changes all three exported functions in
idletrack.c.
In wgaim_set_idlehooks it checks to see if
GetLastInputInfo is present. If it is then the address of
the function is recorded and no hooks are set. If it isn't
then we're running on an old verison of Windows and the
hooks are set as per current behaviour.
In wgaim_remove_idlehooks the module handle taken for
USER32.DLL by wgaim_set_idlehooks is released.
In wgaim_get_lastactive the GetLastInputInfo function
is called, if present. If it isn't present then the hooks will
have run and the shared memory they write to will be
read as per current behaviour. Both methods end up
getting the timer tick of the last user activity, which is
returned as per current behaviour." --Andrew Whewell
committer: Tailor Script <tailor@pidgin.im>
| author | Luke Schierer <lschiere@pidgin.im> |
|---|---|
| date | Sun, 27 Jun 2004 22:29:53 +0000 |
| parents | 7b48e7c07bcf |
| children | 2c6af2767fcf |
line wrap: on
line diff