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

Fix call calculated value invalidation if named ranges are changed (#1536) #1539

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

Pankraty
Copy link
Member

@Pankraty Pankraty commented Oct 6, 2020

Fixes #1536

Previously, when checking if cell cached value has to be recalculated, we only analyzed precedent cells. But if a formula uses named ranges and they start to point to another location, the cached value was not properly invalidated. Now, instead of PrecedentCells, we obtain a collection consisting of named ranges and cells (under IXLVersionable interface) that affect the current cell.

I also had to remove ExpressionCache from CalcEngine because it might store a reference to the old range after a named range was modified.

@igitur
Copy link
Member

igitur commented Feb 22, 2021

Rebased.

@Pankraty Pankraty requested a review from igitur February 24, 2021 11:28
@nghiaphamhn
Copy link

I got this error.. when will the bug be resolved.

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 this pull request may close these issues.

IXLCell.Value returns incorrect value when using formula that references variable that was not yet added.
3 participants