[Xbae-discuss] [ xbae-Bugs-598708 ] examples/list/list2

[SourceForge.net <no...@so...>]

Bugs item #598708, was opened at 2002-08-22 13:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=401980&aid=598708&group_id=31337

Category: Bugs
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Evgeny Stambulchik (evgeny)
Assigned to: Nobody/Anonymous (nobody)
Summary: examples/list/list2

Initial Comment:
In this example, navigation amd traversal don't work.
Also, "Space" operates on the push button instead of
the matrix.

----------------------------------------------------------------------

>Comment By: Danny Backx (dannybackx)
Date: 2003-03-13 22:56

Message:
Logged In: YES 
user_id=39146

I don't see the improvements.
Setting traversal to True doesn't make the focus come back
to the
Matrix - it seems to disappear after a number of TABs.
Also the Space behaviour isn't different.
Am I missing something?

----------------------------------------------------------------------

Comment By: Mark Asselstine (masse_74)
Date: 2003-03-12 21:45

Message:
Logged In: YES 
user_id=134733

I have looked into this issue and have come up with the following. dannybackx your thoughts on this would be 
helpful. The matrix in this case never receives keyboard focus. 

Looking at the code I came to the conclusion that the first mistake was that the "List*mw.traversalOn:" should be 
true. If you have a text widget for example and you set traversal to false the text widget never receives keyboard 
focus. So I starting by enabling traversal.

Second I found that the DefaultAction, xbaeDefaultActionACT does not cause focus to be moved to the Matrix. So 
adding a call in xbaeDefaultActionACT to "XmProcessTraversal( (Widget)mw, XmTRAVERSE_CURRENT )" just 
before the check to DoubleClick() solves this problem. Of course you can check if traversal is enabled for the 
widget before the call.

With these two changes I found the example code now works as expected. And I don't think I broke anything else.

Just out of curiousity as well, why do any callbacks to XmNdefaultActionsCallback only get called when the mouse 
is double clicked in a cell?

Any thoughts on this solution, is it correct or flawed??

Mark

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=401980&aid=598708&group_id=31337