On Thu, Jun 19, 2014 at 12:49:08PM +0200, Hans de Goede wrote:
> Hi,
>
> On 06/19/2014 10:34 AM, Peter Hutterer wrote:
> > On Thu, Jun 19, 2014 at 10:02:30AM +0200, Hans de Goede wrote:
> >> Hi,
> >>
> >> On 06/19/2014 06:57 AM, Peter Hutterer wrote:
> >>> Rather than a single global logging funct
Hi,
On 06/19/2014 10:34 AM, Peter Hutterer wrote:
> On Thu, Jun 19, 2014 at 10:02:30AM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 06/19/2014 06:57 AM, Peter Hutterer wrote:
>>> Rather than a single global logging function, make the logging dependent on
>>> the individual context. This way we won'
On Thu, Jun 19, 2014 at 10:02:30AM +0200, Hans de Goede wrote:
> Hi,
>
> On 06/19/2014 06:57 AM, Peter Hutterer wrote:
> > Rather than a single global logging function, make the logging dependent on
> > the individual context. This way we won't stomp on each other's feet in the
> > (admittedly unu
Hi,
On 06/19/2014 06:57 AM, Peter Hutterer wrote:
> Rather than a single global logging function, make the logging dependent on
> the individual context. This way we won't stomp on each other's feet in the
> (admittedly unusual) case of having multiple libinput contexts.
>
> The userdata argument
Rather than a single global logging function, make the logging dependent on
the individual context. This way we won't stomp on each other's feet in the
(admittedly unusual) case of having multiple libinput contexts.
The userdata argument to the log handler was dropped. The caller has a ref to
the
