Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 494008

Summary:	Zest start/end point hints need to be transferred to the content model when an edge is connected.
Product:	[Tools] GEF	Reporter:	Matthias Wienand <matthias.wienand>
Component:	GEF Zest	Assignee:	gef-inbox <gef-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.2.0
Target Milestone:	4.0.0 (Neon) RC2
Hardware:	All
OS:	All
Whiteboard:

Description Matthias Wienand

2016-05-19 08:09:18 EDT

Currently, the EdgePart within Zest uses the ZestProperties#START_POINT__E and #END_POINT__E as its start and end points when the edge is not connected to source or target nodes. If the edge is connected, then the properties' values are used as hints for the start/end point, influencing the anchor position computation for the connected start/end points.

However, when manipulating the edge using FXBendConnectionPolicy, the start/end point hints are not copied into the zest properties if the edge is connected, i.e. the hints will be removed when the edge is refreshed.

For connected start/end points, the corresponding hint needs to be set as the ZestProperties#START_POINT__E or #END_POINT__E within EdgePart#bendContent() so that it will be set as the start/end point hint within EdgePart#doRefreshVisual().

Comment 1 Matthias Wienand

2016-05-19 10:05:40 EDT

I ensured that the start point and end point hints are correctly transferred to Zest properties within EdgePart#bendContent(). The code is published on the master branch, therefore, I resolve this ticket as fixed for 4.0.0 RC2.