Hi Brian,

> After a break, have managed to get the join working correctly,
> EXCEPT if Cancel is pressed, a copy of the airfoil remains. ???

Where is the airfoil geometry coming from? I mean is it the result of calling factory.update() and then factory.commit() ?

Basically the way the factories are set up, you generally want to call .commit() as the last step when you know that the command has not been canceled. If you have only called .update() on a factory and not .commit() then the output of the factory is removed when the current command ends.


> Do not know why. "Null" is used.

"Null" was used how?


> Maybe has something to do with geometryDatabase?

If you added objects to the geometry database directly by calling geometryDatabase.addObject() then those objects will remain in the database even if your command is canceled - if you've directly added stuff like that rather than using a factory to do it for you, then you will also need to remove them from the geometry database as well on canceling (by calling geometryDatabase.removeObject() ) if you don't want them to be there after the command exits.

- Michael