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.
>
> Any ideas?
>
> Thanks...
> --
Yesterday, I posted the above. I have a little more information to post.
I have the XbaeMatrix widget set up exactly as defined in
Xbae-4.6.2/examples/list. This means I have to following translations
and resources set in the class file:
*mw.traversalOn: False
*mw.translations: <Key>osfUp: SelectCell(Up)\n\
<Key>osfDown: SelectCell(Down)\n\
<Btn1Down>: DefaultAction()
SelectCell(Pointer)\n\
<Btn1Up>: DefaultAction()\n\
<Key>space: SelectCell(Select)
*mw.clip.translations: <Key>osfUp: SelectCell(Up)\n\
<Key>osfDown: SelectCell(Down)\n\
<Btn1Down>: DefaultAction()
SelectCell(Pointer)\n\
<Btn1Up>: DefaultAction()\n\
<Key>space: SelectCell(Select)
When I run the "list" example, it behaves exactly the way mine does. The
arrows keys will not scroll through the list unless the mouse pointer is
located inside the widget. I have tried getting the widget ID of the
text widget and using XmProcessTraversal to put focus on it. No luck. I
did the same with the clip window. No luck. I did the same with the
scroll bar. No luck. Do any of you who have worked on the development of
this widget have any idea what would cause this behavior; and, is there
any way to get around it?
Thanks...
--
Sparta, NC 28675 USA
336.372.6812
http://www.esc1.com
The Gates of hell shall NOT prevail...
