Automate export?

If you have CAD++ with the Cloud Of Points module the solution to this is extremely simple:

1)You populate a COP feature with all of the stuff that you want to have exported automatically
2)You create a COP operator of type "Export"
3)In the COP operator dialog select your COP feature, set the file type, and set the file name.

When the program executes it will bundle all of your features into the COP and export them as specified in the COP operator. Simple as that.

The only trick to this is that in 2013MR1 there is a bug in the file name field for the COP operator that prevents you from using variables in the file name. You can put variables in there and it will work correctly until you close the program. When you reopen the program the variables will have been replaced with whatever the last value was and the field will just be dumb text. The solution is to just let it be dumb text, save the file out to a standard location with a standard name, and then use a File/Move command to move the file to a path and name of your choice. The file/move command will accept variables without an trouble so you can just use this to rename the file and place it wherever you want.

Another bug 2013MR1: The alignment fields in the COP feature and COP operator dialogs don't seem to stick. You can set an alignment but if you close and reopen the dialog it will always default back to the currently active alignment. The solution is to just recall the alignment you want to use for the export right before the COP commands.

Problem solved! .IGES export is now fully automated.

If you have CAD++ with the Cloud Of Points module the solution to this is extremely simple:

1)You populate a COP feature with all of the stuff that you want to have exported automatically
2)You create a COP operator of type "Export"
3)In the COP operator dialog select your COP feature, set the file type, and set the file name.

When the program executes it will bundle all of your features into the COP and export them as specified in the COP operator. Simple as that.

The only trick to this is that in 2013MR1 there is a bug in the file name field for the COP operator that prevents you from using variables in the file name. You can put variables in there and it will work correctly until you close the program. When you reopen the program the variables will have been replaced with whatever the last value was and the field will just be dumb text. The solution is to just let it be dumb text, save the file out to a standard location with a standard name, and then use a File/Move command to move the file to a path and name of your choice. The file/move command will accept variables without an trouble so you can just use this to rename the file and place it wherever you want.

Another bug 2013MR1: The alignment fields in the COP feature and COP operator dialogs don't seem to stick. You can set an alignment but if you close and reopen the dialog it will always default back to the currently active alignment. The solution is to just recall the alignment you want to use for the export right before the COP commands.

Problem solved! .IGES export is now fully automated.