rate limit key presses

[aryadaroui]

keydown autorepeat is too rapid and causes the photo reel to stutter

[0djek]

Could you tell what the problem is? I could look into this

[aryadaroui]

Could you tell what the problem is? I could look into this

the specific issue im referring to is that when a user presses and holds the right arrow key (calling next()), the keydown event will repeatedly be fired and stutter the UI.

The expected behavior would be that when the user holds the key down, it will continuously advance the photo reel by calling next(), but at a reasonable rate. By "reasonable rate", i mean something where:

1. The UI does not stutter
2. The user can quickly advance, but they still have a general sense of their progress through the reel; it shouldn't be disorienting.

I'm envisioning a simple rate limiter in the keydown event listener; but I'm open to other solutions--there are probably a lot

[aryadaroui]

Could you tell what the problem is? I could look into this

@0djek what OS are you on?

[0djek]

I'm on windows.

I'm thinking about some kind of class/functions/something like that, where it would a central place to send these requests and which could track when the button was pressed and if the response was returned from backend. So if user holds the button, the handler would see that the button was pressed earlier, but the response is still pending and it would just discard the event. Later on, when the response is returned, the state of the response could be updated and the events could be handled again.

[aryadaroui]

the +page.svelte kind of does that at the moment for some keys/buttons. You could try to implement it there.

Yes. It really can just be a single function that keeps a timestamp of the last time the event was fired, and if it's outside of some exclusionary time window it'll process the button press, else it'll return

[0djek]

I think that it would be better not to track the time itself between key presses, but track when the request to get next image is completed. It would be more accurate this way