Community
Participate
Working Groups
Build Identifier: 20100617-1415 LabelEditParts in GMF editor disappear when clicking on them and then in empty space. It seems that a label is not refreshed after its direct edit box is disposed. It appears again when the diagram is refreshed (e.g., after moving its owner node). This is new with eclipse 3.6 (GMF 2.3.0), the same code is still working fine with 3.5.2 (2.2.2). Reproducible: Always Steps to Reproduce: 1. Check out the mindmap example (org.eclipse.gmf.examples.mindmap, org.eclipse.gmf.examples.mindmap.edit, and org.eclipse.gmf.examples.mindmap.rcp.diagram) and run it 2. Create a diagram, then a resource node, and give a name for this node 3. Click on the name label and then in empty space
I can confirm this Problem on Windows XP. I think this is very critical since it renders GMF editors useless!
[GMF Restructure] Bug 319140 : product GMF and component UI was the original product and component for this bug
I can confirm the same problem in our own GMF-based editor and also in the Taipan example from the current head. I'm using a Helios Eclipse with GEF 3.6.2 is there any info on this bug or a workaround maybe?
I think it is more related to GMF-Runtime, except if it is because of a listener set by GMF-Tooling.
(In reply to comment #4) > I think it is more related to GMF-Runtime, except if it is because of a > listener set by GMF-Tooling. I see. I thought GEF because of this eclipse.tools.gef post: news://news.eclipse.org:119/i0he9q$bhv$1@build.eclipse.org which mentioned an update of draw2d as the possible culprit
(In reply to comment #5) > (In reply to comment #4) > > I think it is more related to GMF-Runtime, except if it is because of a > > listener set by GMF-Tooling. > > I see. I thought GEF because of this eclipse.tools.gef post: > > news://news.eclipse.org:119/i0he9q$bhv$1@build.eclipse.org > > which mentioned an update of draw2d as the possible culprit ok, seems this is a duplicate of bug #319181
sorry, bug #319191
Yes, I can confirm this is a duplicate. And it is solved in the meantime. So I think we can close this bug, -Johannes
*** This bug has been marked as a duplicate of bug 319191 ***