On Wed, May 11, 2016 at 08:04:35AM -0500, Yong Bakos wrote:
> On May 10, 2016, at 9:51 PM, Peter Hutterer wrote:
> >
> > The initial approach was to allow one surface to be re-used between tools,
> > seats and even used together as wl_pointer cursor surface. This has a few
> > drawbacks, most of
On Tue, May 10, 2016 at 7:51 PM, Peter Hutterer
wrote:
> The initial approach was to allow one surface to be re-used between tools,
> seats and even used together as wl_pointer cursor surface. This has a few
> drawbacks, most of which are related to managing the surface correctly in the
> composit
On May 10, 2016, at 9:51 PM, Peter Hutterer wrote:
>
> The initial approach was to allow one surface to be re-used between tools,
> seats and even used together as wl_pointer cursor surface. This has a few
> drawbacks, most of which are related to managing the surface correctly in the
> composito
The initial approach was to allow one surface to be re-used between tools,
seats and even used together as wl_pointer cursor surface. This has a few
drawbacks, most of which are related to managing the surface correctly in the
compositor. For example, the same cursor surface could have two differen
