Bug 129588 - calc, calculate, dependencies: a cell with a formula should evaluate to the same value regardless where you move (not copy) it into the sheet.
Summary: calc, calculate, dependencies: a cell with a formula should evaluate to the s...
Status: RESOLVED DUPLICATE of bug 81757
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-23 15:41 UTC by b.
Modified: 2020-04-29 18:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description b. 2019-12-23 15:41:43 UTC
Description:
Bug Hunting Session 6.4 RC1: 

this: 

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

quite old bug is still virulent in RC1. 

there are other reports about it, e.g. #129199. 

i'll try to boil down and provide a simplier sheet. 

Steps to Reproduce:
see #81757

Actual Results:
cell calculation neglects formula dependencies (and follows reverse order of cells on sheet? only when iteration is enabled?) 

Expected Results:
cells should be evaluated as good as possible


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.4.0.1 (x64)
Build ID: 1b6477b31f0334bd8620a96f0aeeb449b587be9f
CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: GL; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc: CL
Comment 1 Xisco Faulí 2020-01-10 11:18:46 UTC
Hi b,
to me, it seems the same as bug 81757. What's the reason you created another
bug? Could you please explain the difference between them ?
Comment 2 b. 2020-01-10 21:29:53 UTC
hello Xisco, 

yes, it's the same, 

new is the fact that reordering of cells affects the calculation, i think i'd write that in #81757, perhaps with this hint it's easier to get a handle on it? 

new is that the 'bug hunting session' requested a recheck of old bugs, 

and new is that i was unsure if it's better to add comments to a bug which has been managed as 'new' for five and a half years without progress, or to file a new bug to pull some attention towards it, 

there are plenty reports regarding c-r and iterations, someone should sometimes start to work on it? 

reg. 

b.
Comment 3 b. 2020-01-10 21:38:43 UTC
srry., forgot: 

Eike requestet short concise bug descriptions and doesn't have the time to read through long chains of comments ...
Comment 4 Buovjaga 2020-04-29 18:38:02 UTC

*** This bug has been marked as a duplicate of bug 81757 ***