GNOME.org
 

Re: [orca-list] how to build atspi2 infrastructure

I did that and got 'click'.
I did this without gnome running using my id, not gdm or anything.

Thanks for the hint.

On Tue, 10 Jul 2018 08:11:30 -0400,
Didier Spaier wrote:


Hmm... I would be surprised that the Python version matters, but
who knows.

Anyway type:
gsettings get org.gnome.desktop.wm.preferences focus-mode
If you don't get 'click' as output, but either 'sloppy' or 'mouse',
type:
gsettings set org.gnome.desktop.wm.preferences focus-mode 'click'

Explanation: one could think that the "click to focus" focus mode
has the effect of needing to to use the mouse to focus, but actually it
it has the effect that the last opened windows is raised, then  gets the
focus, which is what we want.

Didier

Le 10/07/2018 à 13:52, John Covici a écrit :

Well, it was gnome-terminal and yes, I could find the button in the
switch window, but no joy as to focus.  I also know it was there
because I could type exit and get out of it.

I am now straightening out python versions -- 3.5 vs 3.6 (I wonder if
orca cares which one?) and once that is done I will see what happens.
The accessibility infrastructure is up to 2.9, so it seems they have
made some significant changes since the 2.6.x I was using before.


On Tue, 10 Jul 2018 07:22:04 -0400,
Didier Spaier wrote:


Then orca could be true, i.e. it would be weird but is possible that
the window of the application started by the command you wrote in
the run dialog doe not get the focus.

Does the same happen if instead of using Alt+F2 you type the command
in a terminal? And can you find this window using the "switch window"
shortcut (Alt+Tab here)?

Didier

Le 10/07/2018 à 12:41, John Covici a écrit :

I know alt-f2iscorrect, I heard orcasay the run dialog.  Itsjust when
I ran a program orca would say no focus.

On Tue, 10 Jul 2018 05:13:12 -0400,
Didier Spaier wrote:


Hello Joyn and all,

I wouldn't assume that this has something to do with the accessibility
stack thus upgrading components at random, taking the risk of muting
your desktop completely ;)

I'd rather first check that the Alt+F2 shortcut us actually bound to
some run dialog. There are various GUI to chck that but it's easier to
use the command line.

For instance try this command:

for keu in $(gsettings list-keys org.gnome.desktop.wm.keybindings); do
    echo "$key = $(gsettings get org.gnome.desktop.wm.keybindings $key)";
done|grep F2

The output I get is:
panel-run-dialog = ['<Alt>F2']

So this is good.

if <Alt>F2 is bound to another command, you can also know what is
currently the shortcut for the run dialog, if any:

for shortcut in $(gsettings list-keys org.gnome.desktop.wm.keybindings); do
    echo "$shortcut = $(gsettings get org.gnome.desktop.wm.keybindings $shortcut)";
done|grep run

Her I get the same output as exepected but if the ru dialog is bound to
another shortcut this will tell you which one.

If I wanted to bind again the run dialog to Alt+F2 I would issue this
command (mind the quoting):
gsettings set org.gnome.desktop.wm.keybindings panel-run-dialog "['<Alt>F2']"

Caveat: I run MATE, not Gnome, maybe the gsettings schemas differ.

Best regards,

Didier


Le 10/07/2018 à 07:36, John Covici a écrit :

Thanks, I do havethosetools already installed, it must have gotten
them on a recent update.

The problems I am having isthat whenever I try to do alt-f2 and run a
program, all orca says is no  focus.  Since gnomeitself seems to be
working, I can go to the top bar, andsee the menus up there and log
out, I figured it was something to do with the accessibility stack.  I
thought trying the latest versions of that might be a good idea.

Thanks.

On Mon, 09 Jul 2018 23:02:29 -0400,
Didier Spaier wrote:


Hello John,

For the most recent versions of the Gnome software meson + ninja are
used instead of autotools as building tools.

As an example on this page:
https://github.com/GNOME/atk

theses commands are suggested (instead of the usual autogen, configure,
make and make install):

    $ meson _build .
    $ ninja -C _build
    # ninja -C _build install

So the first question is: does Gentoo include the Meson and Ninja
software?

If you can get these just try these commands.

Else, you will have to try the latest releases that can be built with
autotools.

Maybe if you elaborate on the kind of trouble you have with the
installed versions or atk, apt-spi2-core and at-spi2-atk and what
these versions are  we can give you more accurate guidance.

Best regards,

Didier

Le 10/07/2018 à 04:22, John Covici a écrit :

I have been having trouble with Orca and the atspi2 infrastructure,
and so I decided to try to build from git.  However neither the core
or atk packages have a configure script nor an autogen.sh script.

How does one build these things nowadays?  I saw something about meson
build, but have no idea what to do with it.

I am suing gentoo and the packages in there are way out of date.

Thanks in advance for any suggestions.


_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org









-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici wb2una
         covici ccs covici com
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]