t; the source client would never exit from the
> loop, making it stuck.
> A timer could free it after some time, but that is not a good solution.
>
> What i need is a way to have a server-side callback when a certain
> client-side event listener returns, all inside libwayland-clie
2013/3/12 Pekka Paalanen :
> On Tue, 12 Mar 2013 12:00:57 +0100
> Giulio Camuffo wrote:
>
>> 2013/3/12 Pekka Paalanen :
>> > On Tue, 12 Mar 2013 11:22:00 +0100
>> > Giulio Camuffo wrote:
>> >
>> >> 2013/3/12 Jason Ekstrand :
>> >> >
>> >> > I'd love to offer some thoughts on the more general drag
On Tue, 12 Mar 2013 12:00:57 +0100
Giulio Camuffo wrote:
> 2013/3/12 Pekka Paalanen :
> > On Tue, 12 Mar 2013 11:22:00 +0100
> > Giulio Camuffo wrote:
> >
> >> 2013/3/12 Jason Ekstrand :
> >> >
> >> > I'd love to offer some thoughts on the more general drag-and-drop
> >> > problem if you want to
the client to issue a request "notify_drop", at the
>> >> end of the drop event listener, which would send the
>> >> "wl_data_source.dropped", but a client that fails to do so would be
>> >> troublesome: when a Qt client starts a drag it goes i
equire the client to issue a request "notify_drop", at the
> >> end of the drop event listener, which would send the
> >> "wl_data_source.dropped", but a client that fails to do so would be
> >> troublesome: when a Qt client starts a drag it goes into a
e.
>>
>> I could require the client to issue a request "notify_drop", at the
>> end of the drop event listener, which would send the
>> "wl_data_source.dropped", but a client that fails to do so would be
>> troublesome: when a Qt client starts a drag
client that fails to do so would be
> troublesome: when a Qt client starts a drag it goes into a loop, which
> is exited only when the data is dropped. If the target client didn't
> send the "notify_drop" the source client would never exit from the
> loop, making it stuck.
>
it from the
loop, making it stuck.
A timer could free it after some time, but that is not a good solution.
What i need is a way to have a server-side callback when a certain
client-side event listener returns, all inside libwayland-client,
without the need for the client app to do anything. Is it
