Re: "[window title] inaccessible": where does it come from, and what does it mean?

Hello, Luca Saiu, le Mon 29 Jun 2015 18:49:00 +0200, a écrit : > window with a window manager (say Marco) the screen reader vocalizes the > window title followed by "inaccessible", and the application state is > not vocalized and doesn't show up in Braille -- I'm using the X11 driver > of brltty,

Re: Signals versus methods in ATK

Hello Alejandro. On 2015-07-01 at 15:11, Alejandro Piñeiro wrote: > After re-reading my email, it is not exactly really well-structured. Don't worry, it was perfectly clear. I appreciate you taking the time to write such a thorough response. Regards, -- Luca Saiu HYPRA -- Progressons ensembl

Re: "[window title] inaccessible": where does it come from, and what does it mean?

On 2015-06-29 at 13:00, Joanmarie Diggs wrote: > Therefore, if you > could file a bug against Orca and attach a full debug.out, I'll look > into it. Thanks! Thank you. And thanks for your response about Braille as well. The idea of looking at the Orca log helped me to understand a few things [1

Re: Signals versus methods in ATK

On 01/07/15 11:15, Luca Saiu wrote: > Hello. > > I see that many if not all ATK state-changing operations are captured by > *both* a method and a signal, conveying the same information by > parameters -- plus a generic user_data pointer for signals. Is not exactly the same information. Methods a

Signals versus methods in ATK

Hello. I see that many if not all ATK state-changing operations are captured by *both* a method and a signal, conveying the same information by parameters -- plus a generic user_data pointer for signals. A good example is the atk_text_set_caret_offset method versus the text-caret-moved signal in