The quickest way is to click on the main window (in order to move the focus away from the description) and then pressing control + tab. So keep control pressed and then press the tab key once. This allows you to move to another opened diagram, and by default it’ll point to the one you used last.
I can’t really answer that because I’m not a VP developer, but I do have a theory…
However, this heavily depends on the kind of diagram we’re using. But I think this is best noted with use case diagrams; especially when connecting 2 use cases.
So my theory is: Visual Paradigm always follows the flow of information, originating from the use case you selected. So everything you do will affect that particular use case:
- Using an association: the flow goes from the original use case onto the new one. It more or less “leaves” the use case. Data must flow here.
- Using an include: once again the flow goes from the original to the new one; the original functionality is being added to the another use case. So we’re more or less still working with the same function.
- Using an extension… Now it’s in reverse (you can also see this by the direction in which the arrow points). That’s because our original use case is the basis (start) of the information flow, our actions affect that use case because that’s where we started.
And an extension doesn’t necessarily mean that all the functionality is being (re)used, only that it’s a possibility that (parts of) the functionality get (re)used. So if we were to extend on another use case we’d basically be suddenly working on a whole new function. Which is a bit illogical because we started our work with the first use case.
So when you drag a resource catalog from a model element then your actions will always directly affect that originating model element. Not necessarily another one.
Anyway, this is not the official explanation of course, but just my theory.
But always keep in mind that VP pretty strictly follows the specifications as they’re set out by the OMG group (depending on the diagram of course). Which is also where I based my theory on.
When you compare this behavior to the official specification then it really makes sense.
I hope I managed to explain that well enough… It’s a very abstract topic.
