Windows idle time

[Florin Ochiana]

I don't want the idle time in my app. In windows in general. I thought OnIdle is called when the application is idle. ----- We are what we repeatedly do. Excellence, then, is not an act, but a habit.

[Rage]

Then you'll have to set a hook on the mouse and the keyboard inputs, that's the only way to know that nothing happened in "windows in general". Search for hook on Code Project (especially the article by J. Newcomer). ~RaGE();

[Florin Ochiana]

Thanks for your time. Regards, ----- We are what we repeatedly do. Excellence, then, is not an act, but a habit.

[avenger_sb25]

I think this might be of some help: GetLastInputInfo The GetLastInputInfo function retrieves the time of the last input event. BOOL GetLastInputInfo( PLASTINPUTINFO plii // last input event ); Parameters plii [out] Pointer to a LASTINPUTINFO structure that receives the time of the last input event. Return Values If the function succeeds, the return value is nonzero. If the function fails, the return value is zero. Remarks This is useful for input idle detection

---

Remember... testing & debugging are always part of programming ...so exterminate those stinking bugs

[Rage]

I'm just curious, where does this comes from ? the online MSDN ? I do not have it in my 2000 version. :doh: ~RaGE();

[Antony M Kancidrowski]

It is in the later MSDN libraries and on-line! :) I know it isn't in the standard MSDN libs that come with VC6. Ant.

[David Crow]

Here is a link to the entire article. However, if you are using Windows 9x or NT, you'll need to employ a system-wide hook. See this article for details.

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

[Anonymous]

GetLastInputInfo not working properly in Windows 2000 Error: Undefined Identifier for GetLastInputInfo please explain Jack

[avenger_sb25]

This is what MSDN says: Requirements Windows NT/2000: Requires Windows NT 3.1 or later. Windows 95/98: Requires Windows 95 or later. Header: Declared in Winuser.h; include Windows.h. Library: Use user32.lib. And what do you mean by not working properly? Can u give details on the improper working? ...Avenger

---

Remember... testing & debugging are always part of programming ...so exterminate those stinking bugs

[David Crow]

Please provide a code snippet of how you are using the function.

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

[David Crow]

avenger_sb25 wrote: Windows 95/98: Requires Windows 95 or later. The function is not available on Windows 9x platforms.

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

[Bharat Gidde]

I am using Windows 2000 here is the snippet #include "stdafx.h" int APIENTRY WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) { LASTINPUTINFO plii; memset(&plii,0,sizeof(plii)); plii.cbSize = size(plii); if(GetLastInputInfo(&plii )) { //code here } return 0; } Even if I declare the LASTINPUTINFO structure in the header file its not working Sandy

[David Crow]

Well, since what you have is not a true Windows application (e.g., you need a window and a message pump), I'm not sure how GetLastInputInfo() is supposed to behave. I may be incorrect, but it wouldn't hurt to at least provide the minimum.

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

[Anonymous]

Even if I provide a window and check the messages it gives a error saying "Undefined Identifier for "GetLastInputInfo() Jack

[David Crow]

Is this a compiler, linker, or run-time error?

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

[Anonymous]

compiler error! Jack

[David Crow]

What other files are being #included in stdafx.h?

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

[Anonymous]

Only the windows.h and the winuser.h Jack

[David Crow]

Have you defined _WIN32_WINNT? If not, look at line #5040 of winuser.h.

---

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)