🚀 go-pugleaf

In article <1992Oct9.154103.18137@sol.ctr.columbia.edu> jerry@connection.prospect.com (Jerry Shekhel) writes:

   Hello out there.  I'm creating a VGA game, and I need precise keyboard
   control, so the kbhit()/getch() functions are insufficient.  I need to know

[...]


   This works, but the problem is that since I'm not using the BIOS to read the
   keystrokes (I'm just reading the key_map[] array), the BIOS buffers them up
   and starts clicking the speaker when the buffer overflows.  Needless to say,
   when I'm holding keys down, this click turns into a "drumroll" and slows down
   my game.  I tried removing the call to old_handler(), but then everything
   stopped working, as if the interrupt itself was no longer being generated.

   Can someone help me with this problem?  Thanks in advance.

Try putting a few getch() statements in there.  These will eat the keyboard
buffer.  Just to make sure you have a key in there to eat, (ie, the user
did not just press <Shift> or something), call (kbhit()) beforehand.  I
usually use the construct:

	for(;kbhit();)
	   getch();

It works well.  Unfortunately, many programmers do not use it, and decide that
the 'drumroll' you describe is a feature rather than a bug ...

		---- tomster@wpi.wpi.edu
--
/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
|  The bleeding hearts and the artists  \ /  Words of Wisdom, Inc.            |
|  make their stand.  And when they've  / \  Thomas R. Dibble, esquire, C.E.O.|
|  given you their all, some stagger &  \ /  aka, The Tomster, Tomahawk, etc. |
|  fall,  after  all,  it's not  easy,  / \  send mail/ money to:             |
|  banging your heart against some mad  \ /  tomster@wpi.wpi.edu              |
|  bugger's wall. ---R. Waters, _Wall_  / \  (or don't send it at all)        |
\vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv/