Skip to content
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

Add support for outline summary direction #304

Closed
mlh758 opened this issue Dec 12, 2018 · 2 comments · Fixed by #307
Closed

Add support for outline summary direction #304

mlh758 opened this issue Dec 12, 2018 · 2 comments · Fixed by #307
Assignees

Comments

@mlh758
Copy link
Contributor

mlh758 commented Dec 12, 2018

Description

By default row outline summaries (the little + box next to the row) appear above the row. There is a sheet setting to flip these below. In Ruby Axlsx this is done by: sheet.sheet_pr.outline_pr.summary_below = false. It would be nice to have the same feature here.

It seems like it would need to go here but I'm not sure how it would be serialized after adding it.

@mlh758
Copy link
Contributor Author

mlh758 commented Dec 13, 2018

It looks like serialization would happen here but I'll need to figure out what to actually call the element. Or trial and error it.

I would be willing to PR this change in once I figure it out.

Edit: For my own reference, the spec can be found on msdn

@mlh758
Copy link
Contributor Author

mlh758 commented Dec 13, 2018

It should end up looking like this:

<sheetPr >
    <outlinePr summaryBelow="0" />
    <pageSetUpPr fitToPage="0" />
...
</sheetPr>

I've got part of an implementation together but it doesn't seem to be saving the attribute within outlinePr.

@xuri xuri self-assigned this Dec 14, 2018
@xuri xuri closed this as completed in #307 Dec 16, 2018
nullfy pushed a commit to nullfy/excelize that referenced this issue Oct 23, 2020
This adds outlinePr support, with the summaryBelow attribute
which defaults to true.

Closes qax-os#304

Signed-off-by: Michael Harris
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants