Keyboard Buffer

[Thargoid]

Does anyone know how to clear the keyboard buffer so that code doesn't try to execute twice?

I've searched online but it seems to be one of those things that's just impossible.

[Ched80]

hey,
Not sure how to clear the keyboard buffer, but I had an issue with a macro that kept executing multiple times. I solved the problem by using a flag in a cell. If the flag was 0 the sub would continue and set the flag to 1. The flag was reset using another sub at a later time. It doesn't solve the problem directly, but the work around helped me.

[Clut]

I have used the same solution as Ched has used.

use a cell somewhere to act as a flag, or status that indicates whether or not somthing is already being processed.
The key is remebering to set the flag when your code starts processing anything, and to clear the flag when your code has finished.

If new code tries to start executing while the flag is set, just exit sub it.

[Faz]

Yep, that's the easiest way i think.

It's like what you should when you add code to the worksheet selection change event. If that code involves selecting other cells then the event will try to run again and again and again, unless you do that and have a variable in there that disables the event to be run again.

[Thargoid]

Excellent - some good ideas - I'll try them out.

I'm trying to drop out of the macro in XLite's docked screens, but it keeps flashing up to say that the sheet's protected if I press "A" (autopilot) multiple times.

Just getting rid of that annoying message box would be good.

[Thargoid]

I solved the problem of the irritating message box.

In the end it's a simple and obvious solution.

As soon as the key (key A) is pressed in the GetASyncKeyState loop, use Application.Onkey to point key A at a macro that doesn't do anything.

When the original macro has finished executing, the remaining A's come barrelling into view only to trigger a case of nothing happening.

...

...

Would a key pointing to such a macro still trigger the KeyState event?

I'm going to have to check that now.

[Faz]

Whenever i use the GetAsyncKeyState function in a constant loop (to check for button presses) if i only want one trigger to occur for each button press, what i do is have a variable in there, perhaps a global variable, to be boolean. For example if the Z key did something like shoot it would be like this...


Private zReleased As Boolean

Private Function checkKeys()
{
   If GetAsyncKeyState(vbKeyZ) Then
   
      If zReleased Then

         Call shootOnce

         zReleased = False

                          End If

   Else

      zReleased = True

   End If
}