[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15499: --------------------------------------- {quote} "if some other client adds other operations, DND won't work" ...do you mean if a third client does it will break or if just we do it ? {quote} If the third client does it, our DND can break. {quote} could we just override mpc and if mpc is installed delegate to its install mechanism ? (but this is definitely starting to be a "dirty" hack :/ ) {quote} I think that isn't possible to do it without patching MPC/Eclipse. DropTraget can be registered only once on one control. {code} target = new DropTarget(Control control, int style) {code} If some plugin registers DropTarget, we can't change or remove it. We can check if a control contains a drop target, add a transfer object(s) and a drop listener (using the API described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=215388). However, the MPC plugin (or some other plugin) doesn't check that. Also, nobody can check if a drop target contains valid operations. We would be able to use MPC's drop target if it used our drop target. Since that isn't the case, MPC DND will fail if our drop target is registered before MPC's target. Can be fixed within the MPC plugin. Currently, it isn't possible (without patching Eclipse) to fix the issue that happens when a drop target is registered with invalid operations. We could ignore it. In the worst case, our DND would work only in the JBoss Central editor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira