[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eswig_helper\u003c/code\u003e module provides C++ classes to interact with the underlying solver, such as customizing logging and solution retrieval.\u003c/p\u003e\n"],["\u003cp\u003eThis module includes classes for defining log callbacks, solution callbacks, and a wrapper for controlling the solution process.\u003c/p\u003e\n"],["\u003cp\u003eUsers can leverage these classes to integrate custom logic with the optimization solver's workflow for advanced control and monitoring.\u003c/p\u003e\n"]]],["The document outlines three C++ classes within the `swig_helper` namespace: `LogCallback`, `SolutionCallback`, and `SolveWrapper`. `LogCallback` likely handles logging actions. `SolutionCallback` probably deals with receiving and processing solver solutions. `SolveWrapper` is expected to encapsulate and manage the solving process. These classes provide functionalities related to logging, solution handling, and wrapping a solver within a C++ context. The documentation is auto-generated.\n"],null,[]]
