On 22.06.2016 11:39, Armin Krezović wrote:
> On 20.06.2016 16:03, Pekka Paalanen wrote:
>> On Sun, 19 Jun 2016 11:33:11 +0200
>> Quentin Glidic wrote:
>>
>>> On 18/06/2016 19:15, Armin Krezović wrote:
Currently, the keyboard client is created and the input
panel surface is set as topleve
On 20.06.2016 16:03, Pekka Paalanen wrote:
> On Sun, 19 Jun 2016 11:33:11 +0200
> Quentin Glidic wrote:
>
>> On 18/06/2016 19:15, Armin Krezović wrote:
>>> Currently, the keyboard client is created and the input
>>> panel surface is set as toplevel on the first output it
>>> finds. This does not
On Sun, 19 Jun 2016 11:33:11 +0200
Quentin Glidic wrote:
> On 18/06/2016 19:15, Armin Krezović wrote:
> > Currently, the keyboard client is created and the input
> > panel surface is set as toplevel on the first output it
> > finds. This does not work in a scenario when there are
> > no outputs,
On 18/06/2016 19:15, Armin Krezović wrote:
Currently, the keyboard client is created and the input
panel surface is set as toplevel on the first output it
finds. This does not work in a scenario when there are
no outputs, resulting in weston-keyboard to crash at
startup due to operating on an inv
Currently, the keyboard client is created and the input
panel surface is set as toplevel on the first output it
finds. This does not work in a scenario when there are
no outputs, resulting in weston-keyboard to crash at
startup due to operating on an invalid output pointer.
This makes input panel
