Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: skiwi on November 03, 2010, 06:55:59 am
-
"you cannot drag a view level package to another location"
(http://i306.photobucket.com/albums/nn245/copperkiwi/Sparx/EA_2010-11-03_08-29-03.png)
why not?
(and yes I searched the help)
-
Bump?
(http://i306.photobucket.com/albums/nn245/copperkiwi/Sparx/2013-10-0109_08_18-EnterpriseArchitectUserGuide_zps3ecb43a8.png)
http://www.sparxsystems.com/enterprise_architect_user_guide/10/getting_started/moveelementsbetweenpackages.html
http://www.sparxsystems.com/enterprise_architect_user_guide/10/getting_started/moveelementsbetweenpackages.html
-
Because it's history. And we know that history can't be changed.
You also can not move a root level. Why? See above.
q.
-
Feature request submitted
-
In the Project Browser the drag operation changes a Package's LEVEL in the model. You drag a Package into whichever other Package you want it to be a child of, whether that Parent is deeper into the model or at a higher level. To change the sequence of peer Packages, use the green up and down arrows in the Project Browser toolbar.
The root node, View and 'model from pattern' are all designed to be the top-level containers of the project. A root node cannot be contained by anything else; a View can only be contained by a root node (and you can drag a View from one root node into another). For those two, you can re-sequence peer-level nodes and views, but you can't drag one peer into another.
A 'Model from Pattern' takes its behavior from where you initially create it - if you create it under a root node, it becomes a View-level container and cannot be subordinate to anything other than a root node. If you create it under a View or any other Package, it becomes a subordinate structure and can be moved to different levels of the model.
So, what exactly are you asking for here? The root node and View do what they are supposed to do, act as top-level containers. The 'Model from Pattern' gives either:
1) A View, but with a type-specific structure or
2) A default structure at any other level in the model
What do you want that you have not got?
-
If I decide I don't want a root node to be a root node any more,
or if I decide to move a view from one root node to another I can't
(see error message shown in previous post).
But I can if I export and import,
so why not make it easy to do within the tool?
-
You CAN drag a View from one root node into another root node, as I said before. You can also drag lower-level structures under one root node into a View or Package under another root node.
So, if you don't want a root node to be a root node any more... what do you want to do? Either create a new root node and drag the contents from the old to the new, or drag the contents of the old root node into another existing root node.
-
I often found that packages on sub-view level would be more useful on view level. But it's not possible to move them up to that level. So restructuring is a real PITA. I'd vote for removing the icons on view level and make them plain packages. Also moving to or from root level seems to be a futile restriction. (I guess it's because a root package has no element.)
q.
-
But I can't drag a view level package to another location in the tree,
why not?