On 11/22/2010 9:16 AM, Chip Orange wrote:
My trick at the moment is to use a combination of the onKeyDown() event to set a flag (similar to yours), and then onKeyProcessedDown() (because it follows shortly afterwards I believe), to reset it, so my macro is allowed to run again if the user causes it to do so.
Why not just use Keyboard.WaitForAllKeysUp? Aaron -- Aaron Smith Product Support Specialist * Web Development GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 260-489-3671 * gwmicro.com To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team.
