Solve bug in data2imgX1 and data2imgX3: account for top padding when adding the columns #3
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
With the previous code each column was drawn (values set to 1) top to bottom starting in px and increasing until bar(I). The starting position was correct, but the ending position was wrong as it didn't account for the column being displaced downwards 'px' pixels.
Same problem found in data2imgX1.m With the previous code each column was drawn (values set to 1) top to bottom starting in px and increasing until bar(I). The starting position was correct, but the ending position was wrong as it didn't account for the column being displaced downwards 'px' pixels.
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.
With the previous code each column was drawn (values set to 1) top to bottom from position
pxto positionbar(I).The starting position was correct, but the ending position was wrong as it didn't account for the columns being displaced downwards
pxpixels.