mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #3] add cell sets wrong format #3
Labels
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/libxlsxwriter#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LaurinStrelow on GitHub (Feb 27, 2015).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/3
Originally assigned to: @jmcnamara on GitHub.
Hi,
consider this example:
This is the result i get:

You may note that the the cells are generated with the wrong format.
This is how it should look like:
I generated the second worksheet with this following code:
Here are the
workbook_add_formatcalls in the same direction, as i later use this format in theworksheet_write_stringcall. This is not the case in the first code example. The bug happens with everyworksheet_write_*method.I also think that this is not bounded to the border style, rather to every style you can set (font, background color, ..).
This example is little bit large, i hope that the issue became clear to you.
This bug happens with and without memory optimization.
If you prioritize which issue you work first on, this is more important for me.
If there is something else i can do to help you, feel free to asks.
Thank you!
@jmcnamara commented on GitHub (Feb 27, 2015):
Hi Laurin,
Thanks, I'll take a look at it.
John
@jmcnamara commented on GitHub (Mar 1, 2015):
Hi,
I've pushed a fix for this to master. I've included a test case based on your report but you can verify it yourself and let me know.
Thanks for the bug report.
John
@LaurinStrelow commented on GitHub (Mar 1, 2015):
Hi,
everything is now working as expected.
Thank you!