Danny Backx <[EMAIL PROTECTED]> wrote:
> Which bug report are you referring to ?
http://sourceforge.net/tracker/?func=detail&atid=108596&aid=231374&group_id=8596
> Also, more clues as to the XbaeInput bug are welcome, I have
> a feeling that you have more info than what you write :-)
Well, not really ;-). I did look briefly into the code, and couldn't see why
translations of the XmText (which the XbaeInput widget is derived from) are not
inherited. As to the other problem of Xbae I mentioned (doesn't matter which
widget is used for the input - XbaeInput or XmText), you can see the incorrect
behaviour when makeing a selection with mouse of a text inside a cell and then
going (with a mouse click) to another cell. The (primary) selection in the first
cell disappears, while it shouldn't.
Another problem is DnD behaviour. For that to work, in the dragging mode, the
focus should change dynamically to a cell which the pointer is moving above.
Otherwise, the drop operation couldn't happen.
In short, ideally, any two cells of a matrix should behave exactly as two
independent text fields.
Regards,
Evgeny
