Created attachment 154768 [details] File to Demonstrate problem with Basic Macro to Solve to target It is possible to call Solver from a macro program and solve for a maximum (and I think minimum) but there is no object one can set such as there is for "solv.maximise = true" I would expect something such as "solve.target = dTarget" I have checked the documentation and forums and used xray and got the list at the end but nothing indicates that a target can be set. Calling solver with the uno does not allow presetting any values so is also not useful. The examples are shown in the file HelloSheet3.ods AssumeNonNegative boolean False SwarmSize long 70 LearningCycles long 2000 GuessVariableRange boolean True VariableRangeThreshold double 3 UseACRComparator boolean False UseRandomStartingPoint boolean False StagnationLimit long 70 Tolerance double 1E-06 EnhancedSolverStatus boolean True AgentSwitchRate double 0.5 DEFactor double 0.5 DECR double 0.9 PSC1 double 1.494 PSC2 double 1.494 PSWeight double 0.729 PSCL double 0 ImplementationName string <...> (get), read-only SupportedServiceNames []string (get), read-only Locale struct (get,set) Document object attribute Objective struct attribute Variables []struct attribute Constraints []struct attribute Maximize boolean False attribute Success boolean False attribute, read-only ResultValue double 0 attribute, read-only Solution []double attribute, read-only ComponentDescription string "DEPS Evolutionary Algorithm" attribute, read-only StatusDescription string "" attribute, read-only PropertySetInfo object (get), read-only Properties []struct (get), read-only Types []type (get), read-only ImplementationId []byte <empty> (get), read-only
Sounds legit, I'll set to NEW. Lingered in UNCONFIRMED for long enough.
Dear Bruce Sobey, 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