Re: [orca-list] MATE Alt+F1 verbosity

Hi Joanmarie,

Le 29/12/2016 à 19:18, Joanmarie Diggs a écrit :
Has anyone any clue what actually happens and leads to those extra

Since events are not generated by Orca, you would need to look at the
apps themselves (i.e. MATE code and behavior).

Yesterday I didn't think it would be MATE's fault, at worse a WM thing
but it's the same with different ones (at least Macro and Compiz).  But
now I realize maybe it's due to how the panel tries not to get focused
for most interactions indeed… but no, now I investigated on that side,
and it's a WM thing.  Marco's docs states that:

For WM_DOCK windows, we do not focus unless we receive a very
explicit request (e.g. Ctrl-Alt-Tab or a _NET_ACTIVE_WINDOW message;
not normal clicks).

Which makes total behavioral sense.  But I guess it's the reason why we
get the issue with the menu, as it probably creates a focused menu for a
non-currently focused WM window.

I of course can provide debug logs if needed, but it's a bit large to
attach on the ML.

Due to size, most people email me privately when they have debug logs to
share with me. Others use a pastebin tool. That said, debug logs are
helpful in answering questions like "What events did Orca get?" and
"What did Orca do in response to an event it received?" The question you
want answered is, presumably, "Why did apps within MATE emit those
events?" So in this case, I don't think a debug log would be helpful.

Well, to be totally honest, actually I don't really care why, I just
want it to be fixed :)  I'm trying to understand why because I thought
it'd help on that, that's all.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]