Bug 135563

Summary: [Calc] Detailed Calculation Settings cannot be reset to default
Product: LibreOffice Reporter: Lenge <Spampot>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: normal CC: stevedee.atwork
Priority: medium    
Version: 6.4.5.2 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Lenge 2020-08-08 17:46:06 UTC
Description:
The options at...
- Tools\Options...\LibreOffice Calc\Formula
- Detailed  Calculation Settings
- Radiobuttons for "Default settings" and "Custom"
- If "Custom" is selected, more settings can be made under "Details..."

... seem to handle both global and per-document settings. However, once a document has "Custom" settings, it cannot be reset to the "Default settings" again.

Steps to Reproduce:
1. Open a Calc document with customized "Detailed Calculation Settings".
2. Go to the above settings and select the "Default settings" radiobutton.
3. Save the document.
4. Re-open the document.

Actual Results:
The document STILL has the "Custom" radiobutton selected.

Expected Results:
The "Default settings" radiobutton should be selected.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
So far only tested on Windows 8.1 Pro 64-Bit with LibreOffice 6.4.5 and 7.0.0.
Comment 1 SteveDee 2020-08-10 02:45:57 UTC
Thank you for reporting this bug.  I can confirm that the bug is present in:

Version: 6.4.5.2 (x64)
Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: en-AU (en_US); UI-Language: en-GB
Calc: CL

and is also present in:

Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-AU (en_US); UI: en-GB
Calc: CL
Comment 2 QA Administrators 2022-08-11 03:47:00 UTC Comment hidden (obsolete)
Comment 3 Lenge 2022-08-17 13:47:16 UTC
(In reply to QA Administrators from comment #2)
> Dear Lenge, [...] QA Team

Re-tested as advised with lastest version 7.3.5.2:
The Bug is still present.