GMF 经验点滴积累（三）- Drag and Drop方式实现图形（Node）的创建

 

 

1、保证Drag源和Drop目标具有同一 Transfer 中介，这里均使用了LocalSelectionTransfer。

 

源为导航TreeViewer组件，这里为简单起见，Tree的input和图形元素使用同一类型模型，因此不涉及模型转换：

 

 public class DragEnableTreeViewer extends TreeViewer implements TransferDragSourceListener { public DragEnableTreeViewer2(Composite parent, int style) { super(parent, style); } public Transfer getTransfer() { return LocalSelectionTransfer.getTransfer(); } protected void hookControl(Control control) { super.hookControl(control); int operations = DND.DROP_MOVE | DND.DROP_COPY | DND.DROP_LINK; DragSource drag = new DragSource(control, operations); drag.addDragListener(this); drag.setTransfer(new Transfer[] { this.getTransfer() }); } public void dragFinished(DragSourceEvent event) { LocalSelectionTransfer.getTransfer().setSelection(null); } public void dragSetData(DragSourceEvent event) { event.data = LocalSelectionTransfer.getTransfer().getSelection(); } public void dragStart(DragSourceEvent event) { LocalSelectionTransfer.getTransfer().setSelection((IStructuredSelection)this.getSelection() ); } }

 

 

 目标为 DiagramDropTargetListener监听器，将其注册到DiagramEditor上

   protected void configureGraphicalViewer() { super.configureGraphicalViewer(); ......... // listen for dropped parts getDiagramGraphicalViewer().addDropTargetListener(new DiagramDropTargetListener(getGraphicalViewer(),LocalSelectionTransfer.getInstance())); }

 

2、这时候已经可以对导航树的节点进行拖拉了，下一步需要容器EditPart对拖拉进行响应，需要安装相应的policy.

protected void createDefaultEditPolicies() { ............. installEditPolicy(EditPolicyRoles.DRAG_DROP_ROLE, new MyDragDropEditPolicy()); }

 

MyDragDropEditPolicy继承自DragDropEditPolicy，需要对getDropElementCommand方法进行重载，如果是同时拖拉多个对象，则需要重载getDropObjectsCommand方法。

protected Command getDropElementCommand(EObject element, DropObjectsRequest request) { IElementType type = ErdElementTypes.XXXX_2001; CreateElementRequest cer = new CreateElementRequest(type); cer.setContainer(((View) getHost().getModel()).getElement()); cer.setNewElement(element); ViewAndElementDescriptor viewDescriptor = new ViewAndElementDescriptor( new CreateElementRequestAdapter(cer), Node.class, ((IHintedType) type).getSemanticHint(), ErdDiagramEditorPlugin.DIAGRAM_PREFERENCES_HINT); CreateViewAndElementRequest req = new CreateViewAndElementRequest( viewDescriptor); req.setLocation(request.getLocation()); Command c = getHost().getCommand(req); return c; }

 

此时，我们的目的已经基本达到了，但是虽然通过将setNewElement将拖拉的模型放在了CreateElementRequest中，但是我们操作结果发现，画板上虽然创建了View，但是模型Element并没有填充进去。

 

3、通过跟踪负责模型创建的ItemSemanticEditPolicy，发现最终问题出在CreateElementCommand上，其不管newElement是否已经存在，总要自己创建一个，问题找到就好解决了，修改其子类XXXCreateCommand，覆盖doExecuteWithResult方法。

private EObject newElement; private EObject container; /** * @generated NOT */ public XXXXCreateCommand(CreateElementRequest req) { super(req); newElement=req.getNewElement(); } protected CommandResult doExecuteWithResult(IProgressMonitor monitor, IAdaptable info) throws ExecutionException { if (newElement==null||!newElement instanceof MyModel) return super.doExecuteWithResult(monitor, info); EReference containment = getContainmentFeature(); EClass eClass = getElementType().getEClass(); if (FeatureMapUtil.isMany(container,containment)) { ((Collection) container.eGet(containment)).add(newElement); } else { container.eSet(containment, newElement); } // Configure the new element ConfigureRequest configureRequest = createConfigureRequest(); ICommand configureCommand = getElementType() .getEditCommand(configureRequest); IStatus configureStatus = null; if (configureCommand != null && configureCommand.canExecute()) { configureStatus = configureCommand.execute(monitor, info); } // Put the newly created element in the request so that the // 'after' commands have access to it. getCreateRequest().setNewElement(newElement); return (configureStatus == null) ? CommandResult.newOKCommandResult(newElement) : new CommandResult(configureStatus, newElement); }

 

 

Ok!Run!上面这点东西折腾了我整整一天，终于搞定！~