| Summary: | Publicly setting the editor input in Diagram Editor | ||
|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | saurav sarkar <saurav.sarkar1> |
| Component: | Core | Assignee: | Project Inbox <graphiti-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | michael.wenz |
| Version: | 0.8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 336488 | ||
| Bug Blocks: | |||
|
Description
saurav sarkar
Marked as enhancement request. This can be tangled earliest after the editor APIs have been refined (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=336488). Even when this is done I'm not yet convinced that this would be a wise thing to do or if we should not better stick to the current paradigm that diagram editors can not be reused. Hi Michael, Thanks for the info. At least making the setInput() protected would help as, so that we can extend the diagram editor and can call the super. We would like to have it urgently as our release depends on this :). If possible i can attach a patch and provide the fix . cheers, Saurav (In reply to comment #2) > Hi Michael, > Thanks for the info. > At least making the setInput() protected would help as, so that we can extend > the diagram editor and can call the super. > We would like to have it urgently as our release depends on this :). > If possible i can attach a patch and provide the fix . > cheers, > Saurav Hi Saurav, well, the setInput method is already protected so you could do as you proposed, can't you? Michael oops..sorry i must have overlooked it :). I will look at it Requested method was already there |