You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @GZLHZ, thanks for your feedback. This issue has been fixed. Please try to upgrade the library with the master branch code, but I don't recommend calling the Save() method in the iteration, which will cause more heap memory allocated.
Hi @GZLHZ, thanks for your feedback. This issue has been fixed. Please try to upgrade the library with the master branch code, but I don't recommend calling the Save() method in the iteration, which will cause more heap memory allocated.
Ok, Thank you. I know that is not a good save way ,I just try it when I learning how to use and report to you.😁 Excelize is a very good project, thank you for create this
nullfy
pushed a commit
to nullfy/excelize
that referenced
this issue
Oct 23, 2020
Description
func SetValueTest() {
// Open Book1 Excel
f, err := excelize.OpenFile("./Book1.xlsx")
if err != nil {
Println(err)
return
}
}
Excute SetValueTest can reappeare the bug.
Steps to reproduce the issue:
1.Create Book1 excel and write a num on D3
2.Excute SetValueTest
3.You can see A3 is empty
if I save after loop, the problem does not exit
for i := 0; i < 10; i++ {
f.SetCellValue("Sheet1", fmt.Sprint("A", i + 1), i)
}
f.Save()
Output of
go version
:go1.12.7.windows-amd64
Excelize version or commit ID:
2.0.1 & update to (2019.07.22)
Environment details (OS, Microsoft Excel™ version, physical, etc.):
win10 1903
office 2019 1906
The text was updated successfully, but these errors were encountered: