The policy in weston in order to determine the chosen DnD action is
deliberately simple, and is probably the minimals that any compositor
should be doing here.
Besides honoring the notify_actions requests on both wl_data_source
and wl_data_offer, weston now emits the newly added events notifying
b
Just a cosmetic: there are mixed coding styles like 'function(...)' and
'function (...)' (space between name function and the parenthesis). It
should be unified, preferably to weston (wayland) coding style (no space)
Cheers,
Marek
On Wed, Mar 18, 2015 at 8:20 PM, Bryce Harrington
wrote:
> On Mo
On Mon, Feb 16, 2015 at 04:37:35PM +0100, Carlos Garnacho wrote:
> The policy in weston in order to determine the chosen DnD action is
> deliberately simple, and is probably the minimals that any compositor
> should be doing here.
>
> Besides honoring the notify_actions requests on both wl_data_so
The policy in weston in order to determine the chosen DnD action is
deliberately simple, and is probably the minimals that any compositor
should be doing here.
Besides honoring the notify_actions requests on both wl_data_source
and wl_data_offer, weston now emits the newly added events notifying
b
