You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 26, 2023. It is now read-only.
First... Thanks! I've been implementing and no problems. Works as advertised in development.
I'd like to see some sugar on top of captureCompound / finishCompound to (optionally) do these calls automatically.
For example: Moving an element with the keyboard (or typing) generates a lot of commands in a short time.
It'd be great to have these options available:
-Auto open captureCompound if two commands are received within N ms of one another
-In this situation, limit commands in the compound to N (or optionally unlimited or N ms timeout)
-Auto finish compound after a non-dupe command is executed
Then certain commands can be flagged as compound by default or something.
I'm sure you considered this but didn't add it for whatever reason. Beyond scope?
First... Thanks! I've been implementing and no problems. Works as advertised in development.
I'd like to see some sugar on top of captureCompound / finishCompound to (optionally) do these calls automatically.
For example: Moving an element with the keyboard (or typing) generates a lot of commands in a short time.
It'd be great to have these options available:
-Auto open captureCompound if two commands are received within N ms of one another
-In this situation, limit commands in the compound to N (or optionally unlimited or N ms timeout)
-Auto finish compound after a non-dupe command is executed
Then certain commands can be flagged as compound by default or something.
I'm sure you considered this but didn't add it for whatever reason. Beyond scope?