[AccessD] shutting down

Any actions that fall through the cracks? 

Susan H. 


> Yes, it's calling a function...actually, a callback function...but as
> far as overhead...unless you were using a 1 mhz machine, it won't be
> noticeable.  It's using a Hook.  The OS has several processes that you
> can 'hook' into.  For example, you can hook into the file system, so you
> can be alerted to whenever a file is read, written too, created, etc.
> That's how 'live' virus scanning programs work.
> 
> At the core level, these mouse and keyboard events are how Access knows
> you are moving the mouse, or pressing a key.  This code 'piggy backs' on
> that process.
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
> Sent: Monday, December 17, 2007 12:41 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] shutting down
> 
> Okay, it looks pretty good -- it considers every keystroke and mouse
> click 
> or mouse movement? Is it going to slow things down the way a bunch of 
> keypress events would? I'm not sure what's happening here -- is this 
> actually calling a function with each key or mouse movement because I
> don't 
> actually see that happening. Can you explain how this works?
> 
> Susan H.
> 
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com