Hi,
Part of a possible future requirement for a project I am currently working
on,  is the ability for users to be automatically logged out of the program
after a specified interval of inactivity. For multi-user purposes, this will
have to be done at the UI level (VB5). I know I could attached Some sort of
procedure on the Mouse and Keyboard events of every Control and window in
the system, but that would be sort of brutal as far as maintainability goes.
Is there away I can get an event from the OS anytime a mouse action or
keyboard stroke is processed within the application or any of it's child
windows? If any of you know how to do it in VB that would be great,
otherwise VC++ would be Ok as well.
Thanks for your help.

Ryan Gallagher
================================
Quadrus Development Inc.
Phone : (403) 459-7158  Fax: (403) 458-5414


================================

w
rite your own screen saver - if the screen saver program is started, there
was a specified interval of inactivity

Use a MessageBlaster it is cheap, good and you can trap ANY message going
to a window

How can I use MessageBlaster ?
Do I have to buy or download from which site ?

It's from Microsoft (free)

Cho, Kwangje heeft geschreven in bericht

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell

Good advice for everyone. rg

--
R. W. Gerling

http://www.rgerling.com
|Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
|neither an expert at MFC win programming, nor C++ programming.  But, I have
|always made it a rule of thumb to declare variables globally.  This will
|almost always cause system errors and the like and it is almost impossible
|to find the source of the errors because you do not know which functions
are
|screwing things up.  Might I suggest passing by reference?  This makes
|things much clearer, and with a little more effort put into the code,
errors
|can be hunted down and destroyed very quickly.  Global variables should
only
|be used when absolutely necessary.  Anyway, give my advice a chance and you
|will almost definitely know what I am talking about!
|
|Nick Maxwell
|
|
|>
|>I've found it to be difficult to capture mouse & keyboard messages
|globally.
|>Lots of system errors - in particular with the Mouse Hook.   Its easy
|within
|>the program hooking the messages.  I have included the sample I tried.  If
|>you have any success, I really like to know.
|>
|>
|>Good Luck - Jack Rasnick

|>
|>
|>
|>
|>
|
|

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell

Hi Jack.  I have my 2 cents to input to the answer of your question.  I am
neither an expert at MFC win programming, nor C++ programming.  But, I have
always made it a rule of thumb to declare variables globally.  This will
almost always cause system errors and the like and it is almost impossible
to find the source of the errors because you do not know which functions are
screwing things up.  Might I suggest passing by reference?  This makes
things much clearer, and with a little more effort put into the code, errors
can be hunted down and destroyed very quickly.  Global variables should only
be used when absolutely necessary.  Anyway, give my advice a chance and you
will almost definitely know what I am talking about!

Nick Maxwell