@antony
This did the trick, thank you.
I still don’t get why users should deal with master/non master views in the first place.
As far as software architects care, all the views of an entity should give them the opportunity to make changes that are then reflected to all the other views. Users always operates on one view at the time, so I don’t see why the current view couldn’t be considered the master one by default.
In other words:
- Visual Paradigm can detect and alert the user that the modified view is not the master one
- The user can then activate an option to make the view as the master one
That’s an annoying, mechanical and manual operation: Visual Paradigm could just activate it, silently, instead of interrupting the users’ thought flow.
