Bug 113561

Summary: In LO CALC it is not possible to integrate the SOLVER into a macro by recording a macro
Product: LibreOffice Reporter: Justin Gray <friendlyinsta>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: normal CC: raal
Priority: medium    
Version: 5.4.2.2 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 64314, 113360    

Description Justin Gray 2017-10-31 21:22:57 UTC 
Description:
Hi, when I record a macro through Tools -> Macros -> Record Macro and use the Solver (Tools -> Solver) while recording the macro, the solver is not properly recorded as part of the macro. If I execute the macro afterwards, the solver is not used in any way, eventhough I used it while recording the macro. Thanks alot for your time and help!

Steps to Reproduce:
1.Record a new macro
2.Use the SOLVER while recording the macro
3.Save the macro
4.Execute the macro

Actual Results:  
The SOLVER operation used while recording the macro is not reproduced by replaying the macro

Expected Results:
The same SOLVER operation used while recording the macro (including the solver settings) should have been performed again by replaying the saved macro.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 5.4.2.2 (x64)
Build-ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4
CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Comment 1 raal 2017-11-01 18:36:52 UTC 
I can confirm with Version: 6.0.0.0.alpha1+
Build ID: e90329ff3896cf33528b47830f49fcd05590bd6a
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;
Comment 2 QA Administrators 2018-11-02 03:51:16 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-11-02 04:36:19 UTC Comment hidden (obsolete)
Comment 4 Rafael Lima 2022-06-01 18:37:24 UTC 
This bug is still valid in LO 7.4.

Although the API to write macros that call the solver are available, it's not possible to automate the solver through Macro Recording.
Comment 5 QA Administrators 2024-06-01 03:15:09 UTC 
Dear Justin Gray,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug