Fix calculation in tickToWord function by applying right shift operat… #1
+2
−2
Conversation
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
…ion to compressed variable
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.
Fix calculation in tickToWord function
Description
This PR fixes an issue in the
tickToWordfunction where the right shift operation was incorrectly applied to the originaltickvariable instead of thecompressedvariable. This caused incorrect word calculation, especially for negative tick values.Changes
tickToWordfunction to apply the right shift operation (>> 8) to thecompressedvariable instead of directly to thetickvariableWhy This is Important
The current implementation ignores the special handling of negative ticks and tick spacing, which can lead to incorrect bitMap positions being calculated. This fix ensures that: