We have a need to use ProProductviewFormattedMdlnameExport() to export to Creo View specified child models of the current assembly while using different recipe files.
ProProductviewFormattedMdlnameExport() lets one do an export of any part or assembly that is currently in memory. It allows one to specify the name and the directory of the exported Creo View file. A ProProductviewExportOptions object is also an input argument. It is used to specify the type of output (ed|edz|pvs|vpz). Currently the only way to specify that a recipe file other than the default ed|edz or pvs|pvz recipe file be used is via a config.pro option like "intf_out_pvs_recipe_file". Unfortunately, setting the config.pro option to point to a recipe file and then changing it again to point to a different recipe file does not work.
I have implemented a workaround that involves pointing to a temporary recipe file that I overwrite as needed.
Before calling ProProductviewFormattedMdlnameExport() I have to overwrite it with my recipe file contents.
After the call I have to overwrite it with the contents of the default recipe file. This is so that a user doing a SaveAs in the UI will get the expected recipe file. This workaround will be broken if the user uses one of the mechanisms for overriding the default recipe files.
So, the request is to add an API that modifies the ProProductviewExportOptions object so that it can optionally contain the fully-qualified name of the recipe file to be used by ProProductviewFormattedMdlnameExport().
