Le 28/08/2019 à 11:07, Gerd Hoffmann a écrit :
...
>> I will try to add a keyboard remapping as we have with VNC because it
>> doesn't work well with my french keyboard (AZERTY). Or perhaps I can use
>> the "button" id instead of the keyid but I don't now how to map the
>> value to a qcode.
>
> De
Hi,
> >> +p = write_short(ib, p, 1920); /* width */
> >> +p = write_short(ib, p, 1080); /* height */
> >
> > Hmm.
> >
> > This is the screen size I guess? Which you don't know ...
> > What this is used for?
> > Should we maybe use INPUT_EVENT_ABS_MAX here?
> >
>
> Yes, it's
Hi,
Le 28/08/2019 à 08:11, Gerd Hoffmann a écrit :
> Hi,
>
>> For instance:
>>
>> section: screens
>> localhost:
>> ...
>> VM-1:
>> ...
>> end
>>
>> section: links
>> localhost:
>> right = VM-1
>> VM-1:
>> left = localhos
Hi,
> For instance:
>
> section: screens
> localhost:
> ...
> VM-1:
> ...
> end
>
> section: links
> localhost:
> right = VM-1
> VM-1:
> left = localhost
> end
>
> Then on the QEMU command line:
>
> ... -object i
This allows to receive mouse and keyboard events from
a Barrier server.
This is enabled by adding the following parameter on the
command line
... -object input-barrier,id=$id,name=$name ...
Where $name is the name declared in the screens section of barrier.conf
The barrier server (barriers)
