Fix for negative toItem variable#92
Merged
Merged
Conversation
Contributor
|
@tchudyk Thank you very much :-) |
Jugen
pushed a commit
that referenced
this pull request
Jun 17, 2021
This file contains hidden or 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.
Sometimes when I'm using lastest RichTextFx, when I select all text in editor, and cut it (ctrl+x), there is throw exception because of negative
toItemvariable.This solution probably is not perfect, but it solve this problem.
I see also here "validation" to not pass values bigger than
cells.size(), so adding validations to not pass values lower then 0 make also sense.Here is a stacktrace for this exception: