We certainly need a reliable way to get the containing layer. In ArgoUML usage we know our layers are of type LayerPerspective, so we can use them to navigate to our Diagram/ArgoDiagram. This is key to what I'm implementing to break the reliance on getCurrentProject() and getActiveDiagram().
> However at the moment we are more likely to just enforce that child > figs have the same layer setting as their parent. Note though that > that should be a one way reference only for child figs. The Layer > should only contain a list of Figs at the top level of the fig > composition hierarchy. I recently changed FigEdgeModelElement.setLayer() to do a setLayer() on all child figs to work around a redraw bug in GEF. Perhaps we need to do this for our other top level Figs too. We could also enhance getLayer to look for the parent FigGroup if the layer field is null, but that would depend on all GEF accesses using getLayer instead of accessing the layer field directly. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
