On 31/12/2013 02:02, Bill Spitzak wrote:
Quentin Glidic wrote:
I use a mouse button as my Push-to-Talk button. This button is
detected as “History back” by my web browser, and *I want to have
both working.*
I think you are confusing what I was complaining about (which was
the idea that there
Quentin Glidic wrote:
I use a mouse button as my Push-to-Talk button. This button is
detected as “History back” by my web browser, and *I want to have both
working.*
I think you are confusing what I was complaining about (which was the
idea that there is some difference between your bind "act
On 30/12/2013 22:51, Bill Spitzak wrote:
Quentin Glidic wrote:
Here is the simple way I think we could solve this problem: a
wl_seat.bind(action) request.
The first important point is here: the client only binds an
*action*. The action is a describing string and does not leak the
key which is b
Quentin Glidic wrote:
Here is the simple way I think we could solve this problem: a
wl_seat.bind(action) request.
The first important point is here: the client only binds an *action*.
The action is a describing string and does not leak the key which is
bound. There would be a set of standard
On 20/12/13 17:24, Quentin Glidic wrote:
> The first important point is here: the client only binds an *action*.
> The action is a describing string and does not leak the key which is
> bound. There would be a set of standard actions, some vendors ones, and
> user custom ones (which application wou
Hello,
With the recent security concerns about the screenshoter interface, a
sibling topic came back to surface: global keyboard/mouse listening.
TL;DR: We need to have a global binding mechanism. I suggest a simple
request to bind an *action* which is fully controlled by the compositor.
The mu
