Hey :),
On Tue, Nov 3, 2015 at 1:36 AM, Jonas Ådahl wrote:
> On Fri, Oct 30, 2015 at 09:55:37PM +0100, Carlos Garnacho wrote:
>> Currently, there's no means for the DnD origin to know whether the
>> destination is actually finished with the DnD transaction, short of
>> finalizing it after the fir
On Fri, Oct 30, 2015 at 09:55:37PM +0100, Carlos Garnacho wrote:
> Currently, there's no means for the DnD origin to know whether the
> destination is actually finished with the DnD transaction, short of
> finalizing it after the first transfer finishes, or leaking it forever.
>
> But this poses o
On Mon, Nov 02, 2015 at 05:46:35PM +0100, Carlos Garnacho wrote:
> Hey!,
>
> On Sat, Oct 31, 2015 at 12:06 AM, Michael Catanzaro
> wrote:
> > On Fri, 2015-10-30 at 21:55 +0100, Carlos Garnacho wrote:
> >> Changes since v1:
> >> - Renamed events to have a common "dnd" namespace.
> >
> > I don't
Hey!,
On Sat, Oct 31, 2015 at 12:06 AM, Michael Catanzaro
wrote:
> On Fri, 2015-10-30 at 21:55 +0100, Carlos Garnacho wrote:
>> Changes since v1:
>> - Renamed events to have a common "dnd" namespace.
>
> I don't think this was a great change. The event occurs on drop, and
> the previous name de
On Fri, 2015-10-30 at 21:55 +0100, Carlos Garnacho wrote:
> Changes since v1:
> - Renamed events to have a common "dnd" namespace.
I don't think this was a great change. The event occurs on drop, and
the previous name described that perfectly, whereas with the new name
it's not very clear how it
Currently, there's no means for the DnD origin to know whether the
destination is actually finished with the DnD transaction, short of
finalizing it after the first transfer finishes, or leaking it forever.
But this poses other interoperation problems, drag destinations might
be requesting several
