Hi Jan,
Thanks for your review. I'll follow up with a new version of some
cleanups related to multiple seats. IM Context patches will follow
later.
Cheers,
Philipp
On Mon, Aug 13, 2012 at 10:10 AM, Jan Arne Petersen
wrote:
> Hi Philipp,
>
> I do not think it is a realistic scenario to have one
Hi Philipp,
I do not think it is a realistic scenario to have one virtual keyboard
surface forwarding the input to different entries depending on which
seat the touch/mouse-event comes from. We would rather have one virtual
keyboard surface per seat (on different outputs). For the demo keyboard
it
This event notifies the input method to which seat it is assigned. This
is necessary to distinguish multiple input methods when multiple seats
are used.
---
protocol/text.xml | 4
src/text-backend.c | 23 +--
2 Dateien geändert, 21 Zeilen hinzugefügt(+), 6 Zeilen entfern