Repository navigation
Including the initiating event in editor change events #76
taylorhadden
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have run across a couple of use cases where I've wanted various aspects of an editor (e.g. when auto-scrolling to match user input) to differ based on whether the event was initiated by a mouse action, or using the cursor keys on the keyboard vs typing.
There are definitely alternative ways to hack this together, but it would be convenient if the
EditorChangeEventcould optionally include the event that initiated the change.This is somewhat similar in concept to the
Sourceenum, which appears to be effectively deprecated as I don't see any references toSource.apiin the codebase.The one potential pitfall I see here is that it would involve lots of changes throughout various modules to actually route in this event.
What does this group think about this idea?
All reactions