Description JSP 2009-04-02 09:18:01 EDT

Build ID: M20090211-1700

Steps To Reproduce:
1.  Click on a node tool on the palette.
2.  Click on the canvas to create the node.
3.  The EditPart for my node extends the AbstractBorderedShapeEditPart.  It has a custom BorderItemLocator that always places its border item directly below the node.  The border item edit part extends LabelEditPart and the figure is a WrappingLabel.
4) The LabelEditPart does not show up until the region where it is located becomes dirty - usually by clicking where you expect the label to be.
5) Any other node that is dropped on the canvas and is  below existing nodes will have the same problem.
6) Any node that is dropped on the canvas and is above existing nodes will not have the problem. 


More information:
I upgraded from GMF 2.1.2 to GMF 2.1.3.

I tracked down the change that is causing my problem.

The layout() method of the BorderedNodeFigure changed from this:
protected void layout() {
if (!this.getBounds().equals(getMainFigure().getBounds())) {
getMainFigure().setBounds(this.getBounds().getCopy());
}
// When parent resizes, cause the border items to be relocated.
getBorderItemContainer().invalidateTree();
erase();
}

To this:
protected void layout() {
if (!this.getBounds().equals(getMainFigure().getBounds())) {
getMainFigure().setBounds(this.getBounds().getCopy());
getBorderItemContainer().invalidateTree();
erase();
}
}

Because my main figure is always the same size as my BorderNodeFigure, the invalidateTree() and erase() method were never being called.  This caused my border item (which is a WrappingLabel) to not be displayed until the region where the item is located becomes dirty - this can be done by clicking the location where you expect the border item to be.