Re: [g-a-devel]KeyNav in Menu Bar Applet (Bug # 74888)
- From: Marc Mulcahy <marc mulcahy sun com>
- To: "Padraig O'Briain" <Padraig Obriain sun com>, hema seetharamaiah wipro com
- Cc: gnome-accessibility-devel gnome org, calum benson sun com
- Subject: Re: [g-a-devel]KeyNav in Menu Bar Applet (Bug # 74888)
- Date: Tue, 26 Mar 2002 10:14:46 -0700
Padraig,
It appears that keynav to and from out-of-process applets in the panel is
broken. Once you've navigated to an out-of-process applet, keynav within
that applet doesn't work. So you can't do a shift-f10 to bring up that
applet's context menus, and it seems that sometimes, you can't press f10 to
get back to the panel. You sorta get stuck in that applet. Any ideas why
this is happening? It's a big show-stopper for me.
Marc
At 11:14 AM 3/26/2002 +0000, Padraig O'Briain wrote:
Hema,
> X-Accept-Language: en
> MIME-Version: 1.0
> To: "Padraig O'Briain" <padraig obriain Sun COM>
> CC: gnome-accessibility-devel gnome org, calum benson Sun COM
> Subject: Re: [g-a-devel]KeyNav in Menu Bar Applet (Bug # 74888)
>
>
> Padriag,
>
> I first set focus in my applet using tab. Then when I press 'f10' - I
> get the first menu.
>
At this point do you use arrow keys or Tab keys or both to navigate the menus?
When using the menu bar applet in a different provess does pressing the
F10 key
get the first menu?
Padraig
> Once I have the menu open... I can use <control> <tab> and traverse
> across applets. Example: from my applet to the foobar widget to clock
> widget and back.
>
> Regards,
> Hema.
>
> Padraig O'Briain wrote:
> >
> > Hema,
> >
> > I would first like to understand how the in-process menu bar applet
works.
How
> > do you get focus on the in-process menu bar applet. Is it by pressing
F10 or
do
> > you just use the Tab keys?
> >
> > My original concern was not with the arrow keys but the initial
problem of
how
> > to get focus on the menu bar applet in the separate process.
> >
> > Padraig
> >
> > > X-Accept-Language: en
> > > MIME-Version: 1.0
> > > To: "Padraig O'Briain" <Padraig Obriain sun com>
> > > CC: gnome-accessibility-devel gnome org, Calum Benson
<calum benson sun com>
> > > Subject: [g-a-devel]KeyNav in Menu Bar Applet (Bug # 74888)
> > >
> > >
> > > Hi,
> > >
> > > The Menu Bar Applet is essentially a menu bar that runs as a separate
> > > process. I am unable to navigate thru the menus in this applet via up -
> > > down arrow keys.
> > >
> > > I created a similar menu bar in an in-process applet and that was
> > > key-navigable. And the same menubar was not navigable in any other
> > > applet that ran as a separate process.
> > >
> > > From Padraig's mail below, I understand that the problem exists because
> > > the up-down key events are received by the panel's Window and are not
> > > getting communicated to the applet which is in a separate Window??
> > > (Padraig, am I right, here?)
> > >
> > > I am not very clear if the bug is a GtkSocket/GtkPlug related or if
> > > Panel should be somehow sending that event to Menu Bar's window?
> > >
> > > Calum, could you also please tell us what you would expect for Menu Bar
> > > Applet?
> > >
> > > Regards,
> > > Hema.
> > >
> > >
> > >
> > > Padraig O'Briain wrote:
> > > >
> > > > Hema,
> > > >
> > > > I am not replying to the issues you raised in your mail, but
rather the
> > keynav
> > > > issues.
> > > >
> > > > I have just made a change to
gnome-panel/libpanel-applet/panel-applet.c
> > which
> > > > should fix the problem I described in bug 72952.
> > > >
> > > > When I run panel-menu-applet the focus is in the PanelApplet as
none of
the
> > > > widgets in the panel-menu-applet can gain focus.
> > > >
> > > > We have a problem with implementing keynav for panel-menu-applet. The
> > applet,
> > > > essentially, consists of a GtkMenuBar whish is running in a different
> > process to
> > > > the panel.
> > > >
> > > > The normal way that keynav works for a GtkMenuBar is that the
keystroke
F10
> > > > causes the first menuitem in the menubar to be selected. A recent
change
> > made to
> > > > GTK+ allows Ctrl+Tab Ctrl+Shift+Tab to cycle through the menubars
in a
> > window.
> > > >
> > > > In our case, the panel-menu-applet is running in a different
process to
the
> > > > panel and is displayed on the panel by using a GtkSocket/GtkPlug (or
> > > > BonoboSocket/BonoboPlug, if you prefer). In any case, the menubar
in the
> > > > panel-menu-applet is in the GtkPlug (which is a GtkWindow) which is a
> > different
> > > > window from the panel's window.
> > > >
> > > > I think we need to discuss with Calum what he would expect to
happen for
> > > > panel-menu-applet.
> > > >
> > > > Padraig
_______________________________________________
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]