System friendly way of disabling repeated key events

[BSzili]

I have a program that uses IDCMP to process key events. This works great for the most part, but the key repeat functionality generates a lot of extra IDCMP_RAWKEY messages when the key is held. I can filter them out based on the qualifier, but the program still has to process all these messages sent to the window's port.
Is there a way to prevent the repeated key IDCMP messages from being sent to the window? One idea that came to mind is a high priority input handler to preprocess the input event, but then I might as well process the events there. A global way to disable key repeat would also work, as this could be toggled when the window is activated/inactivated.

[a/b]

1. Did you try the WA_RptQueue window tag (I think it's KS2.0+)? I haven't messed around with it, but if you set it to 0, would it disable the repeats in your window?
If that doesn't work...
2. Set repeat threshold, via input.device, to a very high value, this would affect everything though.
3. Install a custom handler for input.device with high priority, to handle rawkey events. In your handler you first check if the current window (intuibase->ActiveWindow) is your window. If yes, send a (single) event to your own message port and terminate the chain. If no, do nothing (pass the event down the chain, to input.device's own handler which will then handle the repeats).

[meynaf]

If everything else fails, there is still the possibility to create another, somewhat higher priority task that will get the messages and only forward the ones that are relevant to the main process. This just needs changing the task in the message port (and some way to give key data to the main task).

Of course, at the end everything depends on why these messages are annoying at first place.

[BSzili]

Thanks for all the ideas, I tried WA_RptQueue and it's exactly what I was looking for. If I set it to 0 the window longer receives any repeated IDCMP_RAWKEY messages