Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #91056

Re: need help with an accessibility prototype

Date 2015-05-22 18:39 +0100
From MRAB <python@mrabarnett.plus.com>
Subject Re: need help with an accessibility prototype
References <555F5960.9030501@harvee.org>
Newsgroups comp.lang.python
Message-ID <mailman.230.1432316358.17265.python-list@python.org> (permalink)

Show all headers | View raw


On 2015-05-22 17:29, Eric S. Johansson wrote:
> 2 needs.  first is determining if NaturallySpeaking injects keycodes or
> ascii char into the windows input queue.  second is building a test
> widget to capture and display text.
>
ASCII? :-)

> I think I can solve both of these by building a simple text widget
> (tkinter? qt? ??) to capture keycodes.  problem, is in <mumble><mumble>
> yrs of programming, I've never written a GUI interface so I have no idea
> where to start.  help, tutor, pointers to samples would be most welcome.
>
It injects key events, such as key-down, key-press, key-up.

In my experience, if the widget with the input focus is writeable,
it might capture the text keys itself and the widget's key event
handlers won't see them, only the other key events (up, down, etc), but
if the widget is read-only, the event handlers _will_ see them too.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: need help with an accessibility prototype MRAB <python@mrabarnett.plus.com> - 2015-05-22 18:39 +0100

csiph-web