Mike wrote:
> Looks like the SelectionModel for a Table fires a "selectionChanged" event.
> This is a problem as qx.constant.Event.CHANGESELECTION actually evaluates to
> "changeSelection" (it's missing the 'd'). Just a small incongruity that
> someone might want to fix.
Yes, you're right. This
lycovian <[EMAIL PROTECTED]> writes:
> Looks like the SelectionModel for a Table fires a "selectionChanged" event.
> This is a problem as qx.constant.Event.CHANGESELECTION actually evaluates to
> "changeSelection" (it's missing the 'd'). Just a small incongruity that
> someone might want to fix.
Looks like the SelectionModel for a Table fires a "selectionChanged" event.
This is a problem as qx.constant.Event.CHANGESELECTION actually evaluates to
"changeSelection" (it's missing the 'd'). Just a small incongruity that
someone might want to fix.
Mike
--
View this message in context:
htt