Perhaps the way to think about this is the same way equipment does. For equipment that uses a remote which continuously sends out codes for the duration of the button press, equipment may respond in one of two ways:
1. Some equipment will begin a 'repeat' sequence (similar to holding down a key on a computer keyboard).
2. Other equipment will debounce the button press, and not consider a 'new' button press until a period of inactivity has occurred (similar to the timing scheme you're putting in).
Now, for completeness, other equipment deals with this issue in an entirely other way:
- Some equipment sends a single burst out of the remote for each button press. However, this is the *exception*, not the rule, since it is deemed more frustrating to a user if equipment doesn't respond when a button is pressed simply because the user's remote is still in motion (is being brought up from the couch when the button press begins).
- Other equipment uses the RC-5 protocol, which toggles between two different codes between each button-press.
-Jon