Re: GtkSocket/GtkPlug accessibility

On 09/01/17 14:28, Colomban Wendling wrote:

Thanks for those answers.

Le 29/12/2016 à 11:51, Alejandro Piñeiro a écrit :
But fact is things like MATE-Panel make heavy use of those, so it'd be
nice to have it work properly.

Then perhaps it is about using AtkSocket/AtkPlug on MATE-Panel. But that
is an advice given without looking at all that code.

Okay, I'll see then.  If it's not something that should be done at the
GtkSocket/Plug level and would profit everyone, I might investigate a
different hackish solution that might be good enough for the MATE-Panel
specific problem.  Or see to use AtkSocket/Plug in MATE-Panel's side if
needed, we'll see.

I know I arrive tremendously late to this thread, and I'm not even sure if
this is going to be helpful for your situation, but just in case this is a
small test application I wrote long ago to understand how the whole thing of
AtkSocket & AtkPlug works:

Also, in case it also helps, this is a (long) rant I wrote a while ago too
explaining how we implemented accessibility support in the multiprocess
architecture of WebKit2, also using AtkSocket and AtkPlug:

Now, feel free to dismiss all this if it's totally irrelevant :-)


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