-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Vertically Merging on Tables Causes Incorrect Cell References #564
Comments
@mcxbe, check this fix v0.47.1-beta.2 |
Looks like the above issue is fixed however there still some issues with table merging unfortunately. Take this case for example:
The result should be a 2 row x 3 column table, with cells 0 and 1 being merged on the first row, and cells 1 and 2 being merged on the second row, however the first row of the table ends up with only two cells (cells 0, 1 and 2 merged). Sorry for these weird cases! |
@mcxbe, you do a good job with the quality bug report👍 Thank you. I will take a look later. |
@mcxbe, check this v0.47.1-beta.3 |
I have another one for you sorry!
This one should simply merge the 2nd column vertically, however the 3rd column also gets merged. This behaviour is the same for any column your try to merge, other than the first column. |
@mcxbe, check this v0.47.1-beta.4 |
Hi @ashahabov. Sorry for the late response, I've been away. Had a reasonable play with version 0.48 and can't see any remaining issues. Thanks for your help, I will close this issue. |
When attempting to vertically merge cells in a table, certain merges cause the ATableCell backing field to point to the wrong cell.
To reproduce:
In this code I create a 2 row by 4 column table. I then merge the right-most cells into a single column. Then I attempt to set the fill of cell[1,1] to green, however cell [0,1] changes instead. Also note that
table[1,1] == table[0,1]
becomes true.The text was updated successfully, but these errors were encountered: