You are right - "C Interface". I am known about callback function of "glp_intopt". But it is suitable only for simple MIP problems. If duration of solving of one (relaxation) LP problem grate than 0.2 second then keyboard and mouse in user application is near out of control... Application should get control more frequently.
-----Original Message----- From: Andrew Makhorin [mailto:[EMAIL PROTECTED] Sent: Sunday, October 26, 2008 12:29 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: Re: [Help-glpk] Embedding GLPK to user application > I try to embed #8220;GLPK-solver #8221; to user application. The main > problem is the application #8217;s #8220;hanging up #8221; during > solution process. User what to see solving progress and view best > feasible solution during solving process in his GUI application. With > #8220;lp_solve #8221; this problem solved by using callback functions. > Callbacks raises on each simplex iteration and on each improving solution > found. Programmer may put his code to callback functions to iteration > with user (handling mouse, keyboard and windows events) and fetching > viewing feasible solutions. If callback function return false then > solving process is halted. So, programmer may supply user by > possibilities stop solving process in any moment of time. > How this can be implemented with #8220;GLPK-solver #8221;? In the same way. The glpk mip solver (api routine glp_intopt) allows using the event-controlled callback routine. For more details please see the glpk reference manual, chapter "Branch-and-Cut API Routines". > Are you plan to enhance the DLL-interface of #8220;GLPK #8221;? Glpk is written in the standard C and therefore has no "DLL-interface". It has API, which does not depend on features of a particular operating system. _______________________________________________ Help-glpk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-glpk
