-
Notifications
You must be signed in to change notification settings - Fork 83
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
Tab stops are put in column 1 ignoring the selection (e.g. j=3:8) #635
Comments
Is it possible to set the tab stops for a selection of columns? When I tried doing separate assignments, an error was returned:
And it seems that tab stops are set indeed for the entire table, it ignores the column selection. |
Hello, sorry, we can't reproduce the error. We would need a reproductible example! In the code you shared, you are using |
Dear @davidgohel , To run it the following template will be necessary - that's because I set the overall tabulation width to 0.4. The data:
The code:
It produces the output like this: I attach this file as well. My intention was as below:
So, together, this is what I expect And the file: PS: would it be possible to allow for units in the tab stop definitions? Something like
|
Hello @davidgohel
First of all, thank you wholeheartedly for bringing decimal (and other) tabulation marks into flextable. It is totally a game changer!
And it works perfectly.
Only I noticed one thing. I formatted a table, where the 2 first columns described the content, and the remaining columns held the numeric content.
In the 1st column I prepended the content with "\t" to mimic a nested hierarchy of items. That's very common in my field.
I didn't need any specific positions of tab stops here. Just plain, simple tabs. So I explicitly told flextable to put tab stops only in concrete cells: at the cross of i=1:nrow(data) and j=3:8.
Yet the tab stops were put in the first column too, which spoiled the hierarchy.
Luckily it was enough to select the 1 column and delete the tab stops with a mouse to fix it.
Maybe this issue was caused by the fact that I merged cells in the the 1 row to make a vertical sub-header?
The text was updated successfully, but these errors were encountered: