https://bugs.documentfoundation.org/show_bug.cgi?id=161592

--- Comment #26 from casa <[email protected]> ---
I'm using 26.2.2.2 on windows and this is still a problem.

I have a spreadsheet that runs MATCH against a range of cells.
I always have to hard-recalc for that one cell to get the correct number.

Technically, it seems that [when the spreadsheet changes;including that range
of cells used by MATCH] LibreCalc calcs the MATCH cell/formula *first* in
autocalc sequence before THEN updating the range of cells the MATCH is 'looking
at'.

Normally you would expect LibreCalc to recognize the MATCH formula is 'looking
at' that cell range and should autocalc the range *first* and *then* process
the MATCH.  But it does not.  (Thus the 2nd forced hard-calc is needed (once
the range changes) and then MATCH picks up proper values when it is run the
second time).

Finding and reading this bug (and keying off observations made) I put the exact
same formula (with same reference) in the cell below the first:

B17->  =MATCH(0,K1006:K7005,-1)+1
B18->  =MATCH(0,K1006:K7005,-1)+1

B17 was always the original cell and the one what was always a problem. B18 was
inserting a blank cell and putting the exact same formula there.

Suddenly!  B18 works properly and gives correct value on spreadsheet usage
(normal autocalc of changes), but B17 is always wrong and needs a hard-calc to
update and equal to B18.

This appears to be the same problem that has been discussed in this thread (and
since a POC has already been provided and uploaded it does not appear another
is needed [I cant share the spreadsheet although I could try cutting it down to
a simple test case, but I suspect I will just get what has already been
provided].)

IMO this is a major problem to have something wrong in the calc structure of
LibreCalc such that some formulas in some positions or order work and others do
not...when they are the *same* formula.  Yet discussion and work on this bug
has ceased.

Can it be looked into or reconsidered?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to