Temporary fix for irregular table rows #435
Closed
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.
Possible temporary fix for #242 . Definitely needs testing, but in two test cases this worked fine.
Basically what I did was find the row(s) that had the most number of elements, and store their length.
Then, just before building the table, create a list of empty containers that corresponds to the difference between the length of the row being built and the length of the longest row(s).
Finally, attach that empty container list into the
TableRow
children
property to avoid the irregular sizing error.I left my
print
statements in for debugging if this solution doesn't work for certain cases.