Hi Norman,
thanks for your answer!
> I guess that you are already using the input filter to feed the virtual
> keyboard's events back to nitpicker?
We have not yet implemented the input service as we're yet thinking
about the overall architecture but that would have been our approach.
> Nitpick
Hi Johannes,
> we want to create a virtual keyboard for touch screen devices. This
> shall be done by letting the keyboard provide an input service.
> The problem here is that Nitpicker only provides input to the currently
> active client. Since the keyboard needs to receive input events from the
Hi,
we want to create a virtual keyboard for touch screen devices. This
shall be done by letting the keyboard provide an input service.
The problem here is that Nitpicker only provides input to the currently
active client. Since the keyboard needs to receive input events from the
touch screen, wit