Hi,
So this case currently supported in legacy models is probably something we should try out in our import tests. I can make an evolved version of the PingPong model which defines the replication factor of ports and capsule parts using a constant. Then we can use that model as driver for this work. If this is something that shall be supported, I will update the Bugzillas to clarify that we probably also need a Browse... button next to the Replication field, in the corresponding way as in the legacy tooling, and clarifications how the replication field shall automatically be filled in with the qualified name of the selected constant.
Any opinions about which version of the PingPoing model I shall evolve into using constants in this way?
Regarding any of the other improvements, e.g. to also support the case where the constant is defined in an external headerfile, e.g. as #define (something that the legacy code-generator cannot support) but which has been raised as a needed feature, or the possibility to provide replication factors in target specific transformation configuration files is probably something that we should look into as well. But I guess we start-off with supporting what can be done in the legacy tooling and code-generator.
/Peter Cigéhn