The present version of VWD, when running, blocks a number of Poser functions, like the morph brush, the library, and the material room, to name some. 

Poser functions resume working after pressing 'Stop VWD'. The VWD program then keeps running,but the connection with Poser is lost and there is no way that I can see to restore the contact with Poser. Pressing 'start VWD' again launches a new instance of vWD with an empty scene.

It is not a big problem to do without some of the Poser functions for some time, but it would be great to be able to restore the connection to the current sim, so to have buttons:

- start VWD as it is now,

- suspend VWD with function as 'stop VWD' now is,

- resume VWD as described above

- stop VWD actually terminating the VWD program

obviously, as long as there is only one VWD process, only two buttons would be needed and texts could be swapped. 

It would be nice if two or more VWD processes could exist at the same time so different garments could be accounted for, but that would pose new management problems.

The present version of VWD, when running, blocks a number of Poser functions, like the morph brush, the library, and the material room, to name some. 

Poser functions resume working after pressing 'Stop VWD'. The VWD program then keeps running,but the connection with Poser is lost and there is no way that I can see to restore the contact with Poser. Pressing 'start VWD' again launches a new instance of vWD with an empty scene.

It is not a big problem to do without some of the Poser functions for some time, but it would be great to be able to restore the connection to the current sim, so to have buttons:

- start VWD as it is now,

- suspend VWD with function as 'stop VWD' now is,

- resume VWD as described above

- stop VWD actually terminating the VWD program

obviously, as long as there is only one VWD process, only two buttons would be needed and texts could be swapped. 

It would be nice if two or more VWD processes could exist at the same time so different garments could be accounted for, but that would pose new management problems.

I'll do some more tests but the first ones weren't conclusive.

I'll see what I can do.

It works.
It is now possible to stop the program to perform an action in Poser and then restart it without losing what has already been done.
I can send you the Python files so you can try it out but I don't know how to do it.
If you want, you can give me an email or send me an email on virtualworlddynamics@gmail.com or give me another way to send you the files.

I will send you an email.  

I send an E-Mail to you.

Another wish I would have is that when a simulation was made and transferred to Poser there would be an option to turn that cloth object as an collision object so that we can load the next cloth and make the next simulation.

This is already the case in VWD.
A simulated object with a name with _VWD can be imported as a collision object and will participate in the next simulation.
For example: hair on the character and a _VWD outfit

Yes, I know that way of doing. My question was if you can add a way in WVD to switch the cloth item as collision item. If this would be possible it would allow the user to simply load the next cloth object and simulate again without the need to reload all the collision objects. This would specially be useful if you have multiple cloth items like a pant a skirt and a long top. 

I assume you would like to do all the simulations with just one opening of the VWD program.
For the moment this is not possible because VWD was written to only do one simulation and return the result to the host.
This would represent a lot of work in the program.
Importing _VWD files as a collision object is relatively quick. I'm not sure the time saving is huge.
I'll still think about it.

FVerbass suggested that it would be interesting to have the ability to write Python scripts in VWD.
This can be considered a simple solution that would solve the problem you raise.
There could be a master program which would sequence VWD executions with a minimal number of parameters.
Thus, a set of simulations could be done in a single action.

Yes doing the sim without closing VWD.The idea of having Python access in VWD is very interesting.