Bug 159584 - LibreCalc - Sover Options.. changes should be saved as default for all sheets
Summary: LibreCalc - Sover Options.. changes should be saved as default for all sheets
Status: RESOLVED DUPLICATE of bug 158735
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.2.0.3 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Solver
  Show dependency treegraph
 
Reported: 2024-02-06 04:13 UTC by moe gren
Modified: 2024-03-04 18:01 UTC (History)
1 user (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 moe gren 2024-02-06 04:13:05 UTC
Description:
LibreCalc - Solver Options.. changes should be saved as default for all new sheets or a check box to allow save as default. 

Steps to Reproduce:
1.open solver the options
2.choose any solver engine
3.enter custom values
4. close sheet
5. open a new sheet and enter solver, then options, then engine.

Actual Results:
Use 15 digits of precision on all settings so very tedious to re-enter all fields everytime one needs to run solver. At the present even closing solver requires reentry of option settings. Needs to save changes as default or have a check box to save as default. Also would need a reset default option for newbies.

Expected Results:
Any changes to solver engine options should be permanent. 


Reproducible: Always


User Profile Reset: No

Additional Info:
At least saving custom changes to the individual sheet would be better than what is currently present.
Comment 1 Rafael Lima 2024-02-06 12:57:21 UTC
What solver engine are you using exactly?

Currently solver settings are defined per sheet, meaning that when you define settings for a specific sheet, they're saved and remembered.

However, as pointed out in bug 158735, this is not working for the DEPS and SCO engines. Hopefully this will be fixed soon.

Let me know if fixing bug 158735 will also fix your issue.
Comment 2 Rafael Lima 2024-03-04 18:01:02 UTC

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