[Erp5-report] r36740 kazuhiko - /erp5/trunk/products/ERP5/Document/SolverProcess.py
nobody at svn.erp5.org
nobody at svn.erp5.org
Wed Jun 30 15:05:57 CEST 2010
Author: kazuhiko
Date: Wed Jun 30 15:05:57 2010
New Revision: 36740
URL: http://svn.erp5.org?rev=36740&view=rev
Log:
In buildSolverDecisionList, if we have only one available automatic solver, we just use it automatically.
Modified:
erp5/trunk/products/ERP5/Document/SolverProcess.py
Modified: erp5/trunk/products/ERP5/Document/SolverProcess.py
URL: http://svn.erp5.org/erp5/trunk/products/ERP5/Document/SolverProcess.py?rev=36740&r1=36739&r2=36740&view=diff
==============================================================================
--- erp5/trunk/products/ERP5/Document/SolverProcess.py [utf8] (original)
+++ erp5/trunk/products/ERP5/Document/SolverProcess.py [utf8] Wed Jun 30 15:05:57 2010
@@ -259,6 +259,16 @@ class SolverProcess(XMLObject, ActivePro
new_decision = self.newContent(portal_type='Solver Decision')
new_decision._setDeliveryValueList(movement_dict.keys())
new_decision._setCausality(solver_decision_key[0])
+ # If we have only one available automatic solver, we just use it
+ # automatically.
+ automatic_solver_list = filter(lambda x:x.isAutomaticSolver(),
+ solver_list)
+ if len(automatic_solver_list) == 1:
+ automatic_solver = automatic_solver_list[0]
+ new_decision.setSolverValue(automatic_solver)
+ new_decision.updateConfiguration(
+ **automatic_solver.getDefaultConfigurationPropertyDict(
+ new_decision))
# XXX We need a relation between Simulation Movement and Solver
# Process, but ideally, the relation should be created when a
# Target Solver processes, not when a Solver Decision is
More information about the Erp5-report
mailing list