In 241, if the random port is asked for, this is found by EnSight
In EnSight > 241, if the random port is asked for, this is found by DVS
If the utils is called from PyEnSight, the port is returned together with the thread started
If the utils is called from EnSight, no thread is started and the port cannot be returned since ensight is blocked waiting for data; so I made possible to supply a filename to save the port in in case the user cannot access the ensight console (like in a scripter case)
New version of the previous PR
In 241, if the random port is asked for, this is found by EnSight In EnSight > 241, if the random port is asked for, this is found by DVS If the utils is called from PyEnSight, the port is returned together with the thread started If the utils is called from EnSight, no thread is started and the port cannot be returned since ensight is blocked waiting for data; so I made possible to supply a filename to save the port in in case the user cannot access the ensight console (like in a scripter case)