Well, I retrieved the widet ID of the XmTextField and tried
XmProcessTraversal on that. Do I need to get the widget ID of the
scrolled window? Is that possible?
Danny Backx wrote:
>
> Let me clarify myself, I was pretty vague in my previous message.
>
> XbaeMatrix is actually a whole bunch of widgets, not all of which are mapped,
> depending on the settings. Your situation probably requires the scrollbar
> to receive the keyboard events. But maybe one of the other parts of Xbae
> is getting the event and not doing the right thing with it.
>
> Danny
>
> Danny Backx wrote:
> >
> > Maybe the event is going to the wrong widget ?
> >
> > I'd be interested in the answer because I consider this a bug.
> >
> > Danny
> >
> > Terry Lee Tucker wrote:
> > > I am using Xbaematrix in a database application. I have one problem. I
> > > have to put the mouse pointer somewhere in the matrix widget before I
> > > can scroll up and down in the list using the arrow keys. The list is set
> > > up to act like XmList per the recommendations in the documentation. What
> > > this means, is that the entire row is selected and the cells are not
> > > editable, which is what I want. XmProcessTraversal to put focus on the
> > > widget and be able to scroll with haveing to put the mouse in the matrix
> > > widget. The window in which the matrix widget resides has focus and the
> > > focus policy on my X-Terminal is explicit.
>
> --
> Danny Backx ([EMAIL PROTECTED] [EMAIL PROTECTED])
> Home page : http://users.skynet.be/danny.backx
> Projects: LessTif (http://www.lesstif.org)
> Oleo (http://www.gnu.org/software/oleo/oleo.html)
--
Sparta, NC 28675 USA
336.372.6812
http://www.esc1.com
The Gates of hell shall NOT prevail...
