You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when generating code from UML with nested hierarchy (for AF actors), I've experienced that it generated it in 3 parts. First were created top-level classes, and generation stopped. Then, were generated 2nd layer of hierarchy, and generation stopped. After that, I had to start generation 3rd time, and all classes were generated. But, I had to configure all the classes before generation, and after they were not created, I had to implement configuration again.
I'm not sure, whether such behavior is correct, but if so, then it could be nice to store configuration for all classes before generation. And then, use this configuration when code would be generation from this UML again.
In such case, for example, configuration of icons would be setup once at the 1st generation cycle, and the next times it's not needed to change it.
The text was updated successfully, but these errors were encountered:
Thank you for the reply!
I guess that I'll try to simulate such conditions once more; b/c I'm afraid that I can't send you the entire uml; b/c then I'll need to send rest of the project's files (generated classes were inherited from some intermediated actors)...
Currently, when generating code from UML with nested hierarchy (for AF actors), I've experienced that it generated it in 3 parts. First were created top-level classes, and generation stopped. Then, were generated 2nd layer of hierarchy, and generation stopped. After that, I had to start generation 3rd time, and all classes were generated. But, I had to configure all the classes before generation, and after they were not created, I had to implement configuration again.
I'm not sure, whether such behavior is correct, but if so, then it could be nice to store configuration for all classes before generation. And then, use this configuration when code would be generation from this UML again.
In such case, for example, configuration of icons would be setup once at the 1st generation cycle, and the next times it's not needed to change it.
The text was updated successfully, but these errors were encountered: