-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
nsid is generated incorrectly for abstract num #1358
Comments
Hi, would you like to contribute? |
Sorry, no, I do not have time to be a contributor. I would like to fix this bug for you though, but the only thing you have to do is to change the 4 into a 0. I cannot push my change to your repo since I do not have permissions. |
This is how Pull Request works. You don't need permission for commit in one repo. Anyway, if you don't have time, it's fine. |
I mean that I have a local branch with the fix, but that I cannot push it:
|
You should fork the repo, make changes in your fork and then create a PR to main branch |
Like I said, it's just a single character to change, so I think creating a fork just for that is a bit much. But here you go: |
…ract-num Fixed bug raised in issue #1358
NPOI 2.7.0
File Type
Reproduce Steps
The issue is illustrated by the following example code: In the top example the lower bytes are used, which change between successive calls. The bottom example uses the higher bytes, which will not change quick enough.
Issue Description
I ran into an issue when creating abstract num instances. The constructor will assign an nsid based on the current tick count, but the wrong 4 bytes are used, which result in successive identical identifiers.
The issue can be found here:
https://github.com/nissl-lab/npoi/blob/master/OpenXmlFormats/Wordprocessing/Numbering.cs#L974
The text was updated successfully, but these errors were encountered: