On Thu, 8 Dec 2016 16:01:55 -0600
Derek Foreman wrote:
> On 08/12/16 02:54 PM, Pekka Paalanen wrote:
> > On Thu, 8 Dec 2016 13:28:41 -0600
> > Derek Foreman wrote:
> >
> >> On 02/12/16 02:07 AM, Pekka Paalanen wrote:
> >>> IMO, your check
On 08/12/16 02:54 PM, Pekka Paalanen wrote:
On Thu, 8 Dec 2016 13:28:41 -0600
Derek Foreman wrote:
On 02/12/16 02:07 AM, Pekka Paalanen wrote:
On Thu, 1 Dec 2016 17:19:41 -0600
Derek Foreman wrote:
Check that all the objects in an event
On Thu, 8 Dec 2016 13:28:41 -0600
Derek Foreman wrote:
> On 02/12/16 02:07 AM, Pekka Paalanen wrote:
> > On Thu, 1 Dec 2016 17:19:41 -0600
> > Derek Foreman wrote:
> >
> >> Check that all the objects in an event belong to the same client as
>
On 02/12/16 02:07 AM, Pekka Paalanen wrote:
On Thu, 1 Dec 2016 17:19:41 -0600
Derek Foreman wrote:
Check that all the objects in an event belong to the same client as
the resource posting it. This prevents a compositor from accidentally
mixing client objects and
On Thu, 1 Dec 2016 17:19:41 -0600
Derek Foreman wrote:
> Check that all the objects in an event belong to the same client as
> the resource posting it. This prevents a compositor from accidentally
> mixing client objects and posting an event that causes a client to
>
Check that all the objects in an event belong to the same client as
the resource posting it. This prevents a compositor from accidentally
mixing client objects and posting an event that causes a client to
kill itself.
It's intended that the compositor killing itself be easier to debug
than the