Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: Paolo F Cantoni on April 18, 2019, 05:09:43 pm
-
We already have a number of behaviour toggles for objects in diagrams.
- Selectable
- Printable
- Dockable
I'd like to propose a couple more.
- Movable - default yes. Determines if the Selectable object is able to be moved. This would cut down on the micro-movements that occur accidentally and cause the diagram to b marked as "modified" when conceptually it shouldn't be.
- Frameable - default yes. Determines if the object is to appear in a Diagram Frame (created from this diagram).
Increasingly, we find that certain administrative objects (such as Title Blocks, Keys and Legends etc.) are needed for the correct maintenance of the diagram within the repository, but are superfluous (and even counterproductive) when the diagram is viewed within a diagram frame.
We've tried marking them as not printable, but that doesn't work. In any event, the two scenarios are not congruent.
Thoughts?
Reported,
Paolo
-
Though I can follow you with your intentions I fear that adding more features to a feature overflowing tool having lots of bugs will end up in an - hmmm - even more feature overflowing buggy tool.
q.
-
I support these suggestions. I would find them most useful.
I'd like to think there was a better way of preventing micromovements though
-
What is the scenario is there for having something selectable but not movable?
-
resizing, editing ?
good question though, I'd like "not movable" to be defined as not draggable, but continue to allow alignment and movement using cursor keys.
-
resizing, editing ?
good question though, I'd like "not movable" to be defined as not draggable, but continue to allow alignment and movement using cursor keys.
Yes, that was my intent. It's the mouse dragging micro-movements that I'm trying to eliminate here.
As to selectable but not moveable scenario, in addition to skiwi's points, there's multiple selection. Micro-movements are really annoying here.
Paolo