| Forum: Graphiti |
|---|
| Topic: Graphiti as RCP |
|---|
| Re: Graphiti as RCP [message #1060766 is a reply to message #1060576] |
Tue, 28 May 2013 07:45 |
Michael Wenz Messages: 1275 Registered: July 2009 Location: Walldorf, Germany |
Senior Member |
|
|
Andrej,
not sure if that is what you mean: if you want the '*' on the editor tab to
disappear after saving, that is controlled in the editor's isDirty method.
Returning false there will hide the *. A call to that method should be
triggered after saving by firing a prop-dirty-event (simply call
firePropertyChange(IEditorPart.PROP_DIRTY) on your editor). The default save
implementation does exactly that.
Michael
|
|
|
| Topic: How to keep active the model outline |
|---|
| Re: How to keep active the model outline [message #1060767 is a reply to message #1060580] |
Tue, 28 May 2013 07:48 |
Michael Wenz Messages: 1275 Registered: July 2009 Location: Walldorf, Germany |
Senior Member |
|
|
Andrea,
the examples.common plugin implements an exemplary outline. See packages
org.eclipse.graphiti.examples.common.outline and
org.eclipse.graphiti.examples.common.outline.tree.
This should give you an idea how to activate the outline page you want to
see.
Michael
|
|
|
| Topic: AddFeature in Palette |
|---|
|
| Topic: Moving shapes and bendpoints |
|---|
| Moving shapes and bendpoints [message #1060858] |
Tue, 28 May 2013 12:54 |
Hernan Gonzalez Messages: 148 Registered: October 2010 Location: Buenos Aires, Argentina |
Senior Member |
|
|
In the current implementation DefaultMoveShapeFeature moves also the bendpoints of those FreeFormConnections that originate from the current moving shape and terminates in another selected shape (and hence is presumably part of the same movement).
This seems quite ugly to me, on several levels:
- it couples the DefaultMoveShapeFeature to a particular connections implementation
- it must resort to an ugly hack to guess if that connection is to be "moved", asking, (inside a MoveShapeFeature) the editor for its current selected shapes so as to guess the full set of shapes that are being moved
- the related utility methods are private, so it's difficult to alter the behaviour by overriding
- the bendpoints movement is done directly, not via the MoveBendpointsFeature - so, if (as it was my case) we have the connections with its bendpoints as part of the bussiness model, and relied on MoveBendpointsFeature to keep that in sync, we are rather screwed
I call the attention to this issue, in case the Graphiti developers (supposing they agree) can think on something better - I'm not sure if this has some simple solution. In retrospect, I think it would have been more convenient to specify BendPoints in relative coordinates, with respect to the connection start, but I guess it's too late to change this.
[Updated on: Tue, 28 May 2013 12:57] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.01625 seconds