On 11/27/2012 09:11 PM, Kristian Høgsberg wrote:
> On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
>> From: Jan Arne Petersen
>>
> text: Rename and extend text_model key event
I'm holding off on this one and the remaining patches. I think you're
right that it's
On 11/28/2012 03:50 AM, Kristian Høgsberg wrote:
> On Tue, Nov 27, 2012 at 03:11:17PM -0500, Kristian Høgsberg wrote:
>> On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
>>> From: Jan Arne Petersen
>>>
>> text: Rename and extend text_model key event
> I'm holding off on
On Tue, Nov 27, 2012 at 03:11:17PM -0500, Kristian Høgsberg wrote:
> On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
> > From: Jan Arne Petersen
> >
> > >>> text: Rename and extend text_model key event
> > >> I'm holding off on this one and the remaining patches. I think you
ines under 80
characters; introduce temporary variables instead of building up
several nested calls and break inner loops into helper functions if
the nesting gets too deep.
Kristian
> Jan Arne Petersen (8):
> text: Start input method from configuration
> text: Rename and extend text_mo
From: Jan Arne Petersen
Signed-off-by: Jan Arne Petersen
---
clients/Makefile.am | 2 +
clients/keyboard-utils.c | 173 +++
clients/keyboard-utils.h | 67 ++
3 files changed, 242 insertions(+)
create mode 100644 clients/keyboa
t: Rename and extend text_model key event
text: Send more information with keysym events
text: Add support for grabbing the keyboard
text: Add support for forwarding key events
window: Add utils for xkb keyboard input
window: Allow to get xkb context from display
text: Add simple com
It appears that both the input method and the client have to do the xkb
decoding from hardware events to keysyms and shift information. And that
the method used by the input method to produce "other" keys is to, in
effect, run xkb backwards to produce fake hardware events from the
desired resul
On 11/15/2012 11:29 AM, Jan Arne Petersen wrote:
> My current idea would be to add a modifier_names event to text_model, so
> that an input method sends an array of known modifier names (which would
> be the same used by xkb_keymap_mod_get_index). The mapping to a bitmask
> is than just done by th
From: Jan Arne Petersen
Signed-off-by: Jan Arne Petersen
---
clients/Makefile.am | 2 +
clients/keyboard-utils.c | 173 +++
clients/keyboard-utils.h | 67 ++
3 files changed, 242 insertions(+)
create mode 100644 clients/keyboa
han just done by the index of that modifier name in the array.
Regards,
Jan Arne
Jan Arne Petersen (8):
text: Start input method from configuration
text: Rename and extend text_model key event
text: Send more information with keysym events
text: Add support for grabbing the keyboard
text: Add
On Mon, Nov 05, 2012 at 03:26:38AM +0100, Jan Arne Petersen wrote:
> From: Jan Arne Petersen
>
> Hardware keyboard input allows input methods to grab the keyboard
> and process hardware key events to generate text events (with
> pre-edit) over the same text_model interface we use
From: Jan Arne Petersen
Signed-off-by: Jan Arne Petersen
---
clients/Makefile.am | 2 +
clients/keyboard-utils.c | 173 +++
clients/keyboard-utils.h | 67 ++
3 files changed, 242 insertions(+)
create mode 100644 clients/keyboa
From: Jan Arne Petersen
Hardware keyboard input allows input methods to grab the keyboard
and process hardware key events to generate text events (with
pre-edit) over the same text_model interface we use for the virtual
keyboard. This allows input methods which compose multiple key
events for
On Dec 14, 2010, at 2:20 AM, Stefanos A. wrote:
>
>
> 2010/12/14 Mike Paquette
> On Dec 13, 2010, at 4:47 PM, Daniel wrote:
>
> > Any thoughts on keyboard input?
>
> I recently completed work on a novel window system not too different from
> Wayland. We ran
2010/12/14 Mike Paquette
> On Dec 13, 2010, at 4:47 PM, Daniel wrote:
>
> > Any thoughts on keyboard input?
>
> I recently completed work on a novel window system not too different from
> Wayland. We ran across a number of potentially desirable features and
> behaviors
On Dec 13, 2010, at 4:47 PM, Daniel wrote:
> Any thoughts on keyboard input?
I recently completed work on a novel window system not too different from
Wayland. We ran across a number of potentially desirable features and
behaviors regarding keyboard input.
* Keyboard mapping/translation
16 matches
Mail list logo