`on:combo` bug - `Shift-ArrowRight` multiple times... about svelte-keydown HOT 8 OPEN

The solution (#4) is to keep track of keys that are currently pressed and reset combo when no keys are pressed down.

Published to NPM in v0.3.1

from svelte-keydown.

@metonym Why can't you handle it normally?
Creating an additional variable spoils all the transparency of the solution.

from svelte-keydown.

@lukaszpolowczyk Can you submit a PR with your preferred solution?

from svelte-keydown.

@metonym It turns out that I just can't install version 0.3.1
There is 0.3.0 in npm: https://www.npmjs.com/package/svelte-keydown

In the previous comment, I thought the reason was different. Sorry.

It works fine here:
https://metonym.github.io/svelte-keydown/#on%3Acombo

Looks like you just need to update the npm database.

from svelte-keydown.

@lukaszpolowczyk No problem – try installing 0.3.1 now from npm

from svelte-keydown.

@metonym It's better, but there is still some bug.
Steps:

1. Press and hold Shift
2. At the same time, I press ArrowRight
3. I release ArrowRight
4. Press ArrowRight
5. I release ArrowRight

And the effect is:

So despite releasing ArrowLeft, it is still saved in combining.

The bug is because I'm holding Shift.

from svelte-keydown.

So your expected behavior would be to preserve the Shift key but not ArrowRight/ArrowLeft after releasing?

from svelte-keydown.

@metonym I want this effect:

Because I am holding the Shift button but releasing the ArrowRight/ArrowLeft button.

If (holding Shift) I let go of ArrowRight and then hit ArrowLeft, then ArrowRight should disappear from the latest combination.

I have two separate shortcuts:
Shift-ArrowRight
Shift-ArrowLeft
And they call separate functions that I alternate without letting go of Shift because that would be inconvenient and unintuitive.

from svelte-keydown.