ribes [Wed, 20 Jan 2010 16:05:16 +0000 (16:05 +0000)]
- Adding a new method to SALOME_ResourceManager:
//! Add a new resource to the resource_manager
/*!
write -> true, resource manager will add it into a xml_file
xml_file -> could be empty, in this case if write is true, resource manager will write
the resource in its first ResourceCatalog file
*/
void AddResourceDefinition(in ResourceDefinition new_resource, in boolean write, in string xml_file)
raises (SALOME::SALOME_Exception);
vsr [Thu, 17 Dec 2009 11:57:56 +0000 (11:57 +0000)]
Fix a problem of RTTI data initialization in the libraries loaded by Python (SWIG-modules, etc). Additional fix: dl module can be unavaiable in Python.
vsr [Wed, 16 Dec 2009 13:24:29 +0000 (13:24 +0000)]
Fix a problem of RTTI data initialization in the libraries loaded by Python (SWIG-modules, etc). Without this change, dynamic_cast<..> operator does not work that can cause runtime error (like crash or incorrect operating of some functionality).
caremoli [Thu, 8 Oct 2009 14:29:01 +0000 (14:29 +0000)]
CCAR: add the PyNode object that can be created in a container
to execute remote Python code.
Example from python interpreter:
import salome_pynode
code="""def f(x):
return 2*x
"""
node=container.createPyNode("mynode",code)
y=node.execute("f",10)
CCAR: add a timeout for DSC/CALCIUM reads
If a read (cplxxx) is waiting more than the value given by the environment
variable DSC_TIMEOUT, the read is interrupted and an exception is raised.
If DSC_TIMEOUT is not set or its value is 0, the timeout is infinite.
It is possible to set the timeout by using the properties of the component.
The value of a property is set in an environment variable with the same
name by a call to beginService
CCAR: add trace file for DSC/CALCIUM calls
Trace file is written by default on stderr and can be redirect to a file (automatic name)
by setting the environment variable DSC_TRACE to 1
Trace can be desactivated by setting the environment variable DSC_TRACELEVEL to 0
CCAR: Correction of a problem with management of genericobj in SALOMEDS
- Move the management from SALOMEDS_Study_i interface to SALOMEDSImpl_Study interface to
be sure to be called in all situations : embedded or standalone
- Register and Destroy genericobj on calls to SetValue (AttributeIOR) but also when
an AttributeIOR is removed
CCAR: Modify FindOrLoadComponent so that all modes be coherent (with parameter structure or with string).
If the machine is not given, the default machine is the machine of the resources manager
and not the local machine as it was done in the string mode.
CCAR: translate some comments in english
add the local path of a file in the python sys.path before executing it (execfile(srcname) in runSalome.py)
remove supervisioncontainer launch
CCAR: replace the old way to take the python global interpreter lock
by calls to PyGILState_Ensure/PyGILState_Release in C++ container
so that GIL management be coherent from GUI embedded interpreter to embedded
python container.
CCAR: add a message in case of error when loading a component.
The dlerror output for dlopen plus the traceback for the import of the python module
The import_component python function now returns a string instead of a boolean.
If the string is empty, the import is OK.
The C++ code in container MPIContainer and ParallelContainer has been adapted.
