Little changes to FlxDebugger code completion.
#3222
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, typing out a simple line in the console, (e.g.
FlxG.state.exists = false;) and pressing enter will result in code completion automatically adding a phrase to your command, instead of just running it. (resulting in e.g.FlxG.state.exists = false;clearBitmapLog)To fix this I simply added a case to
CompletionHandler.hxthat closes the code completion if the current command ends with;.This pull requests also makes a change to
CompletionList.hxthat allows you to press TAB (along with ENTER) in order to fill in the currently selected completion. This is a common bind in a lot of other programs.