Eclipse Community Forums: Eclipse Platform » usage of dropAssistant for org.eclipse.ui.navigator.navigatorContent

Home » Eclipse Projects » Eclipse Platform » usage of dropAssistant for org.eclipse.ui.navigator.navigatorContent

usage of dropAssistant for org.eclipse.ui.navigator.navigatorContent [message #336996]

Mon, 20 July 2009 09:03

Eclipse User

The org.eclipse.ui.navigator.navigatorContent can have a drop assistant
however it is only triggered when attempting to drop something
corresponding to possibleChildren. I want to be able to slurp a file and
import everything from it into the database represented by on tree
element. That tree element will not get a file as a children after this
operation. In fact my database element will NEVER EVER have files as
children. So it feels very wrong to add that as a possibleChildren. Is
that what I am supposed to do anyway? What other strange effects will that
have? I don't want my tree to be able to contain files in some strange
corner case...

Re: usage of dropAssistant for org.eclipse.ui.navigator.navigatorContent [message #486792 is a reply to message #336996]

Sat, 19 September 2009 00:54

Eclipse User

Jonathan wrote on Mon, 20 July 2009 09:03

Don't get too hung up on the name possibleChildren. This is what triggers the drop assistant, so that's the property way to do it. If there are no actual children provided, then there will be no side effects.

Previous Topic:	Common Navigator fails to refresh on addition/deletion
Next Topic:	Referenced class not on plugin classpath

Goto Forum:

-=] Back to Top [=-

Current Time: Mon May 05 23:48:31 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter