| Summary: | Request.getExtendedData() is cleared between concurrent invocation of LayoutEditPolicy.showLayoutTargetFeedback | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Robert Kwolek <R.Kwolek> |
| Component: | Misc | Assignee: | gef-inbox <gef-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Robert Kwolek
The extended data is meant to be used during the handling of one event such as a mouse drag. If it weren't cleared, it would contain meaningless data from some previous event/mouse location. What are you storing? I'm storing (or I was storing, see next sentence) a figure which shall be displayed during moving an edit part. In such case there is a workaround (or rather correct implementation ;-)): I can use LayoutEditPolicy.createChildEditPolicy. Another example: I'm using the extended data to store a source connection anchor which shall be modified during creation of a connection basing on the selected target edit part. And in this case the extended data is not cleared. For me the extended data was a kind of "request persistent storage" but in fact there is no guarantee that some internal GEF module will not remove my data. So, maybe there should be a comment, that the extended data is not meant to be used "externally" (outside GEF), or maybe the places where it is cleared could be specified?... |