We consume that event intentionally so that it doesn't reach the table view.
I'm still thinking through this - I don't really love the current design and I'm thinking that maybe it would be better to have beginEdit(), endEdit(), and isEditing(). Not sure yet. G On Dec 1, 2010, at 5:06 PM, Chris Bartlett wrote: > Do you mean that you have to wait for the row editor slide effect to finish > before you can select another row? > > If so, try commenting out line 97 of org.apache.pivot.wtk.content > TableViewRowEditor > consumed = true; > (in the ContainerMouseListener#mouseDown() method) > > Does that give you the behaviour you want? > > Chris > > > On 2 December 2010 03:57, lello <[email protected]> wrote: > > Greg, just checked you update. > It works fine for me without any effect. > With an effect on (horizontal_slide) it has one issue. When I first select a > row with the mouse then the I can see the slide effect. However, when I > double click (or just single click) with the mouse on a new row, the > previous editor is disabled but no new editor shows up, and I have to wait a > bit then click again, then the roweditor is there. > > For my application it works, as I am not using the effect anymore. > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/TableView-selectedRowChanged-tp1992938p2002063.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com. >
