Re: [platform-swt-dev] DragSource and 'promised data'

[Silenio Quarti <Silenio_Quarti@xxxxxxxxxx>]

It is not a big problem. I believe motif
works like that, so you can check how it was done there.

But I think possible to implement "promised
data" by providing a owner when calling "NSPasteboard.declareTypes:owner:"
and implementing the selector "pasteboard:provideDataForType:".
I just looked  quickly look so I might be wrong.

Silenio

Scott Kovatch <skovatch@xxxxxxxxx>
Sent by: platform-swt-dev-bounces@xxxxxxxxxxx

09/15/2008 09:33 PM

Please respond to
"Eclipse Platform SWT component developers list."        <platform-swt-dev@xxxxxxxxxxx>

To	"Eclipse Platform SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
cc
Subject	[platform-swt-dev] DragSource and 'promised data'

Hi,

Looking at the Carbon implementation of DragSource, Transfer objects that
aren’t of type FileTransfer aren’t asked to provide their data until
the drag actually starts, and the drag callback is invoked. In Cocoa, it’s
different: you have to provide the data up front on the NSDragPboard when
you start the drag.

I guess the consequence of this is that the Transfers will always be asked
to provide the data, even if the drag isn’t completed. Does this matter?
I don’t see anything DragSourceListener.dragSetData that implies it is
only called after the drag is completed, but I thought I’d ask.

Scott

--------------- 
Scott Kovatch
Flex Engineering
Adobe Systems, Inc.
skovatch@xxxxxxxxx

I am Scott Kovatch, and I approved this message._______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev