Check user activity ( mouse - keyb ) but not as spyware
-
I need to check the activity of the user, to detect when the user is outa here. I need it to set away mode in software. But I don't want to hook all messages like spy software. is there any way to detect the ser activity ? Screen saevr detection is not an good way. Pavel Sokolov http://crea70r.photosight.ru
-
I need to check the activity of the user, to detect when the user is outa here. I need it to set away mode in software. But I don't want to hook all messages like spy software. is there any way to detect the ser activity ? Screen saevr detection is not an good way. Pavel Sokolov http://crea70r.photosight.ru
How about
GetLastInputInfo()?
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
How about
GetLastInputInfo()?
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
It's very good, but "Windows 95/98/Me: Unsupported." I understand that support of these systems is almost stopped, but my customers have all range of systems. Maybe I will emulate this function for Win9X - Anyway thank you very much. Pavel Sokolov
-
It's very good, but "Windows 95/98/Me: Unsupported." I understand that support of these systems is almost stopped, but my customers have all range of systems. Maybe I will emulate this function for Win9X - Anyway thank you very much. Pavel Sokolov
Pavel Sokolov wrote: Maybe I will emulate this function for Win9X See here.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
Pavel Sokolov wrote: Maybe I will emulate this function for Win9X See here.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
Thank you! Just found it ;) Pavel Sokolov
-
Pavel Sokolov wrote: Maybe I will emulate this function for Win9X See here.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
I read that article and he puts the hook handler handles and counter into shared memory: #pragma data_seg (".IdleUI") // any name you like HHOOK g_hHookKbd = NULL; HHOOK g_hHookMouse = NULL; DWORD g_dwLastInputTick = 0; #pragma data_seg () Why is that? Doesn't that mean that only one thread of a single process can use the hook handler in this DLL? Why aren't those data at least process-specific so multiple applications could have used the functions in the DLL? I recently made a mouse hook handler and I did NOT put anything like this in the shared data segment and it works fine. Do you think that was something specific for the Windows 9X support?
-
I read that article and he puts the hook handler handles and counter into shared memory: #pragma data_seg (".IdleUI") // any name you like HHOOK g_hHookKbd = NULL; HHOOK g_hHookMouse = NULL; DWORD g_dwLastInputTick = 0; #pragma data_seg () Why is that? Doesn't that mean that only one thread of a single process can use the hook handler in this DLL? Why aren't those data at least process-specific so multiple applications could have used the functions in the DLL? I recently made a mouse hook handler and I did NOT put anything like this in the shared data segment and it works fine. Do you think that was something specific for the Windows 9X support?
Blake Miller wrote: Why aren't those data at least process-specific so multiple applications could have used the functions in the DLL? That would defeat the purpose of checking for idleness. If these variables were not marked as shared, each process that used the DLL would get its own copy of the variables, thus idle in one process might not be idle in another process.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown