The 'mangle.ini' file contents should be part of the model.

[vkrawciw]

It is madness that each time there is a product update that the 'mangle.ini' file is overwritten on each client machine thus wiping out certain code generation preferences. Also, when more than one person is working on the same model it is madness that they could create different code because their mangle.ini file is different. All the settings in this file should be preferences set in the model itself so that everyone creates consistent code and code generation is unaffected by Integrity updates.

[PatrickOllerton]

Thanks for the product idea Victor. The original intent of having the mangle preferences in a file separate from the model was to make it simple and efficient to re-use the definitions across all models. And when a new model is created, the correct mangling is already setup. If the mangle definitions were contained in the model then you need a way to populate that model with the mangle definitions that you want. We'll do some more investigation into use cases and implementation options.

[vkrawciw]

I understand what you are getting at there and indeed that functioonality is also useful. But the big problems for me are:

1. When an update for modeller is installed the files get wiped out.
2. Until a developer realises that problem 1 has occurred, he is creating different code to all other developers for the same model.
3. Fiddling about with ini files should be consigned to Windows 3.1 !
   

[tdalon]

Are you talking about PTC Integrity product or another PTC product? Maybe it is posted for the wrong product?

[vkrawciw]

Definitely PTC Integrity Modeler - specifically regarding the C++ generation.