Minor optimizations and fix lines being cut when newlines are in the string #43
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
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.
Listening to the Menu Keys seems unecessary when the key is 0, and this thread uses quite a bit of resources with the native calls, so simply returning when the key is zero seems like a good options here.
The other commit changes the line split to a regex, this might be more performant (haven't tested that), but the main point with this is that if new lines are in the string it would still cut off the string, that seems unecessary, this fixes that by also seeing new lines as whitespace characters and replacing the new line with a new line giving you more control over where the new lines are.