[news.eclipse.tools.gef] Re: Need meta key info

["Randy Hudson" <none@xxxxxxxxxx>]

> Well a Link would imply dropped instances to be linked.  Thats what I am 
> looking to imply, though linking means not necessarily what you specified 
> in the context of my application.
>
> Because their is the idea of 'linking' and my app uses 'linking' I want to 
> stay consistent with the method the user would normally use when dropping 
> something and trying to create a link.
>
> I say the COPY set there.  But the listener seems to be completely aware 
> that the only action would be copy.  So I fear the change will be more 
> complicated.

I'm sure linking makes sense in your application.  But why linking 
templates?  Can't you use some other transfer and your own drop listener? 
What are you actually linking?

> I see.  I guess I had used the awt system before and was used to it. Now I 
> gotta get a feel for this swt one which is slightly different. Like when 
> dropActionChanged() is called, how do I get an indication of what it was 
> changed to?  in the awt system, there is an event object passed into this 
> method and you can tell from that.  But here there is no way to know, nor 
> reject the new action if you dont want it, AFAICT!?

Our "handle" methods are similar to the way we designed our tool 
implementation.  You can access the last event by calling getXxxEvent(), and 
then look at the detail to see what the new type is.

The handle methods are slightly higher-level, and involve sending requests 
to target editparts.  The "raw" receiving method is more low-level and does 
things such as resetting the timer for interpreting a mouse hover.