Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should be able to check if the index in the caret position is valid in the ctor. #2101

Open
andy840119 opened this issue Aug 18, 2023 · 1 comment
Labels
code quality Improve code quality. enhancement New feature or request Good for contributor Those issues does not UX or behavior-related, so did not need lots of discussion.

Comments

@andy840119
Copy link
Member

andy840119 commented Aug 18, 2023

image

For example, here's the TimeTagCaretPosition.
Need to :

  • Check if TimeTag is in the Lyric
  • Also, add valid index and invalid index check in the shared test case.
  • CompareTo should check the index of time-tag in the lyric, not compared by index.
@andy840119 andy840119 added the enhancement New feature or request label Aug 18, 2023
@andy840119 andy840119 added this to the 2023.0909 milestone Aug 18, 2023
@andy840119 andy840119 added the code quality Improve code quality. label Aug 27, 2023
@andy840119
Copy link
Member Author

[Update]

  1. The change index out of range logic is already in the CaretPositionAlgorithm.PositionMovable().
  2. It might be possible to give the caret position in the caret position algorithm. Using try-catch in the algorithm is not a good idea.
  3. check the check-caret-index-is-valid-in-caret-position in my repo.

@andy840119 andy840119 added the Good for contributor Those issues does not UX or behavior-related, so did not need lots of discussion. label Aug 27, 2023
@andy840119 andy840119 removed this from the 2023.0909 milestone Sep 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Improve code quality. enhancement New feature or request Good for contributor Those issues does not UX or behavior-related, so did not need lots of discussion.
Projects
None yet
Development

No branches or pull requests

1 participant