Bugzilla – Full Text Bug Listing
| Summary: | canAddBendpoint() = false has strange behaviour | ||
|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Hernan Gonzalez <hjg.com.ar> |
| Component: | Core | Assignee: | Tim Kaiser <tim.kaiser> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | matthias.gorning, michael.wenz |
| Version: | 0.8.0 | Flags: | tim.kaiser:
juno+
|
| Target Milestone: | 0.9.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | Juno M3 theme_bugs | ||
Added a refresh in ConnectionBendPointEditpolicy. This updates the connection's edit part after an erasure of source feedback. This brings the desired effect of snapping back if the addition of the bend point is not possible. Also two deprecation warnings were removed and the respective algorithm improved. Part of M3, not M2 Bookkeeping: Set target release Part of Graphiti 0.9.0 (Eclipse Juno) |
This can be reproduced by simply coding public boolean canAddBendpoint(IAddBendpointContext context) { return false; } in our AddBendpointFeature, e.g. in the Tutorial. When one selects a FreeFormConnection and tries to manipulate it adding and moving several bendpoints, the method canAddBendpoint() is indeed called, but the user has no visual feedback, it seems that the bendpoints are correctly added, they can be moved, etc. Only when one clicks outside the connection, to deselect it, the phantom bendpoints disappear and the connection returns to its original shape.